# The two binaries `make build` writes into the repository root, and the three
# scratch directories abuild works in: with `source=""` and
# `builddir="$startdir"` (see APKBUILD) it unpacks into ./src, stages the
# package into ./pkg and keeps ./tmp for the toolchain caches it redirects —
# i.e. all three live inside the checkout it is packaging, and abuild exports
# GOTMPDIR=$startdir/tmp, so every `go build` puts its work directory there.
#
# Listing them is not tidiness. Go records vcs.modified in every binary built
# inside a repository and reads that flag from `git status --porcelain`, which
# counts UNTRACKED files — so one untracked directory left beside the build is
# what stamps a released binary "-dirty" for the life of the apk.
/specsrht
/specsrht-migrate
/src/
/pkg/
/tmp/

# Transient build artifacts
*.tmp

# Local instance config
/config.ini

# Git worktrees. Both spellings, because the tooling picks either one and a
# worktree that shows up as untracked invites somebody to commit a checkout.
/.worktrees/
/.claude/worktrees/

# Local bare repos and the bleve index + render cache. Both are the service's
# runtime state, not source; the cache is safe to delete at any time.
/repos/
/cache/

# The stylesheet is build output, not source: `make css` regenerates it from
# scss/main.scss and a `base` partial that belongs to the deployment's
# core.sr.ht version, so committing it would pin the chrome to whichever
# version its author happened to have materialized.
#
# BOTH names have to be here. Only the intermediate main.css was, and the
# content-hashed file `make css` renames it to is the one that survives — it is
# written by the APKBUILD's build() BEFORE `go build`, so every packaging run
# used to compile the binaries with an untracked file sitting in the tree.
/web/static/main.css
/web/static/main.min.*.css

# Beads / Dolt files (added by bd init)
.dolt/
*.db
.beads-credential-key
.beads/proxieddb/