chore: untrack prog binary and fix stale ignore rules - #5
Merged
Merged
Conversation
The compiled `prog` binary (13 MB) was tracked in git, so every local rebuild surfaced as a modified file and invited accidental commits of build output. The cause is a rename that was never finished: the `# Binary` section of `.gitignore` still listed `/tasks` and `/cmd/tasks/tasks` from when this project was called `tasks`. Neither path exists anymore, so no ignore rule covered either of the current build targets, and the root binary was committed at some point without anything flagging it. This drops `prog` from the index with `git rm --cached`, leaving the file in place on disk, and repoints the two existing ignore lines at the real targets, `/prog` and `/cmd/prog/prog`. Scope: index and ignore rules only. No source, schema, or behavior changes. The binary blobs remain in history, so this does not shrink the repository — that would take a separate history rewrite. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The compiled
progbinary (13 MB) is tracked in git, so every local rebuild shows up as a modified file and invites committing build output by accident. It was sitting dirty in the working tree when I found it.The cause is an unfinished rename. The
# Binarysection of.gitignorestill listed/tasksand/cmd/tasks/tasks, names from when this project was calledtasks. Neither path exists in the tree anymore, so no rule covered either current build target and nothing flagged the root binary when it was committed.What changed
git rm --cached progdrops the binary from the index. The file stays on disk, so nobody loses their local build./progand/cmd/prog/prog. The untrackedcmd/prog/progwas never committed but was also never ignored; it is now.Two files, two lines changed, plus the deletion.
Before / after
Before,
git statusin a freshly built checkout reportedM progand?? cmd/prog/prog. After, both are ignored and the tree is clean after a build.Scope
Index and ignore rules only — no source, schema, or CLI behavior changes. Releases are unaffected:
.goreleaser.yamlbuilds from./cmd/progfor linux/darwin on amd64/arm64 and ships tar.gz archives, so the committed binary was never the distribution path.The binary blobs remain in history, so this does not shrink clone size. That needs a separate history rewrite, deliberately not attempted here.
🤖 Generated with Claude Code