russell@unturf.com
c383c41f92
Each feature commit was being followed by a "bump GIT_HASH to X" commit whose value was always one behind HEAD (the bump itself shifted HEAD again). The file in git was effectively a stale record that setup.py overwrote on every CI install anyway via `git rev-parse --short HEAD`. Pure churn — half the commit log was these bump commits. Untrack the file, .gitignore it, drop the bump from CLAUDE.md's AUTO-PUSH and post-work-chores guidance. setup.py keeps writing the real HEAD at install; views/version.py still reads it. The /version endpoint behavior is unchanged — it just stops requiring a follow-up commit per ship.
47 lines
692 B
Text
47 lines
692 B
Text
# my ignores.
|
|
*.sqlite*
|
|
vars.fish
|
|
vars.sh
|
|
|
|
# GIT_HASH is rewritten by setup.py at install time via
|
|
# `git rev-parse --short HEAD`. Tracking it just produced churn:
|
|
# every feature commit was followed by a "bump GIT_HASH to X" commit
|
|
# whose value was always one commit behind HEAD (because the new
|
|
# bump commit itself shifted HEAD again). setup.py owns this file.
|
|
make_post_sell/GIT_HASH
|
|
|
|
*.egg
|
|
*.egg-info
|
|
*.pyc
|
|
*$py.class
|
|
*~
|
|
.coverage
|
|
coverage.xml
|
|
build/
|
|
dist/
|
|
data/
|
|
data*/
|
|
src/
|
|
.tox/
|
|
nosetests.xml
|
|
env*/
|
|
tmp/
|
|
Data.fs*
|
|
*.sublime-project
|
|
*.sublime-workspace
|
|
.*.sw?
|
|
.sw?
|
|
.DS_Store
|
|
coverage
|
|
test
|
|
|
|
*.dkim.key
|
|
|
|
caddy
|
|
.claude
|
|
|
|
monero-wallet-cli.log
|
|
monero-wallet-rpc.log
|
|
monero-wallet-rpc.log*
|
|
|
|
|