Remove committed __pycache__ .pyc artifacts from 0ce199e and add gitignore entries #25
Labels
No labels
blocked:needs-attention
blocked:needs-decision
bug
chore
in-progress
quickfix
security/high
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AuWoMe/forgeflow#25
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Summary
Commit
0ce199e(kilo-gsd follow-up for #23) accidentally tracked compiled bytecode artifacts. Found by post-deploy probe (kanban cardt_5ecf9aa6).Actual behavior
The following binary blobs are tracked in the repo (verified with
git ls-files):tests/__pycache__/test_pre_commit_loop_detector.cpython-311-pytest-9.1.1.pyc(~26KB)tests/__pycache__/test_pre_commit_loop_detector.cpython-312-pytest-8.3.4.pyc(~23KB).gitignorehas no__pycache__/or*.pycentry, so a kilo-gsdgit addswept them in.Expected behavior
No compiled artifacts in git history;
.gitignorecontains__pycache__/and*.pyc.Reproduction steps
cdto repo rootgit ls-files | grep -E "__pycache__|\.pyc$"→ shows the two .pyc pathsImpact
Binary blobs will rot and cause merge noise. Cleanup should
git rm --cachedthe files, add gitignore entries, and commit.Filed by reporter lane from kanban card
t_5ecf9aa6(post-deploy probe of #23).Resolved on main. Commit
4519ce6("chore: ignore pycache and untrack stale pyc artifacts") already untracked the .pyc blobs and added both__pycache__/and*.pycto .gitignore. Verified:git ls-fileson origin/main shows zero tracked pycache/.pyc paths, andgit check-ignore -v tests/__pycache__matches.gitignore:33:__pycache__/. Closing.