chore: stop tracking the compiled shots binary
Release / Build and publish image (push) Failing after 10m0s

8.9 MB of macOS binary in the repository root, committed by accident in
a8e523b. The source in tools/shots is the thing that matters, and it is
still there.

Ignored as well as removed, because `go build ./tools/shots` without -o
writes the binary to exactly this path — which is how it got committed the
first time, and would be how it got committed the next.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Kristian Wind
2026-08-17 19:44:19 +02:00
co-authored by Claude Opus 5
parent 4276892590
commit a2f4de02fc
2 changed files with 5 additions and 0 deletions
+5
View File
@@ -45,3 +45,8 @@ node_modules/
# the process is killed, which during a hung build is exactly what happens. One
# was committed by accident.
/web/vite.config.js.timestamp-*.mjs
# A compiled `go build ./tools/shots` in the repo root. It was committed once by
# accident — 8.9 MB of macOS binary — and `go build ./tools/shots` without -o puts
# it right back.
/shots
BIN
View File
Binary file not shown.