clawbot
935e18c6f1
check / check (push) Successful in 3m28s
`make fmt` formatted only Go, so the org's Markdown settings were unenforced and Markdown was wrapped by hand. prettier, pinned in `package.json` and `yarn.lock` beside ESLint, now formats the Markdown with `.prettierrc` (4-space tabs, `proseWrap: always`). It runs only in Docker: `make fmt` writes the formatted files back without a bind mount, and `make fmt-check`, `make check` and the image build fail on unformatted Markdown. The image build's lint stage now runs the Go format check directly and no longer installs `make`. `README.md` and `TODO.md` are reformatted with no word changed: the README reflows from 72 to 80 columns. Model: opus-5-5
31 lines
1.0 KiB
Plaintext
31 lines
1.0 KiB
Plaintext
# .git is sent so the build can derive the version it stamps into the binary
|
|
# (script/version). Its config, which can hold a remote URL carrying a
|
|
# credential and which `git describe` does not need, is left out of a
|
|
# directory context. A context sent as a tar is not filtered by this file, so
|
|
# it carries .git/config unless its sender leaves it out.
|
|
.git/config
|
|
|
|
# No tracked file may be listed here: git in the build would see it as
|
|
# deleted and mark the version -dirty.
|
|
#
|
|
# .ci-fingerprint is deliberately NOT excluded: it is the CI cache barrier
|
|
# that keeps the check stages from replaying a cached pass. See the lint
|
|
# stage of the Dockerfile.
|
|
bin/
|
|
# Extracted from 3p/ by `make assets` inside the build; a host copy is not
|
|
# needed. The tarball in 3p/ must stay in the context.
|
|
static/js/alpine.min.js
|
|
# The js-deps stage installs ESLint and prettier; a host copy would overwrite
|
|
# them at the `COPY . .` of the stages built on it.
|
|
node_modules/
|
|
.env
|
|
.env.*
|
|
*.db
|
|
*.sqlite
|
|
*.sqlite3
|
|
.DS_Store
|
|
.idea/
|
|
.vscode/
|
|
tmp/
|
|
temp/
|