chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Repo hygiene: gitignore core dumps + ignore agent state in docs/architecture/ #172

New Issue
Open
opened 2026-05-14 04:55:25 +00:00 by chihlasm · 0 comments
chihlasm commented 2026-05-14 04:55:25 +00:00
Owner
Copy Link

Cleanup carried forward across multiple sessions. The working tree consistently has these untracked items that should never be committed but currently warn on every git status:

  • core.144926, core.145678 (20MB core dumps at repo root, 2026-05-07)
  • docs/architecture/core.1392564 (20MB core dump under an otherwise-legit docs subdir, 2026-05-13)
  • docs/architecture/.remember/ (agent skill state, not source)

Two small changes:

  1. Add to .gitignore: 
    core.[0-9]*
**/.remember/
  2. Delete the existing files locally (rm core.144926 core.145678 docs/architecture/core.1392564 -rf docs/architecture/.remember/). The repo never tracked them, so there's no history to preserve.

Quick-win — single PR.

Cleanup carried forward across multiple sessions. The working tree consistently has these untracked items that should never be committed but currently warn on every `git status`: - `core.144926`, `core.145678` (20MB core dumps at repo root, 2026-05-07) - `docs/architecture/core.1392564` (20MB core dump under an otherwise-legit docs subdir, 2026-05-13) - `docs/architecture/.remember/` (agent skill state, not source) Two small changes: 1. Add to `.gitignore`: ``` core.[0-9]* **/.remember/ ``` 2. Delete the existing files locally (`rm core.144926 core.145678 docs/architecture/core.1392564 -rf docs/architecture/.remember/`). The repo never tracked them, so there's no history to preserve. Quick-win — single PR.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
10x-analysis
From 10x product analysis
 backend
FastAPI/Python work
 bug
Something isn't working
 collaboration
Team sharing, escalation, notifications
 database
PostgreSQL/schema changes
 documentation
Documentation updates
 duplicate
This issue or pull request already exists
 enhancement
Improvement to existing feature
 feature
New functionality
 frontend
React work
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 integration
PSA, external service integrations
 intelligence
Analytics, AI, data-driven features
 invalid
This doesn't seem right
 priority: high
Do this soon
 priority: low
Nice to have
 priority: medium
Important but not urgent
 question
Further information is requested
 quick-win
Low effort, high value
 strategic
Long-term strategic bet
 ux
User experience improvements
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chihlasm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#172
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?