clawbot
74a96b2226
check / check (push) Waiting to run
`REPO_POLICIES.md` binds the repo to a JavaScript styleguide, but nothing checked `static/js/`. ESLint, pinned by `package.json` and `yarn.lock`, now lints it with the styleguide's two checkable rules, `no-var` and `prefer-const`. It runs only in Docker on a digest-pinned node image: a `js-deps` stage installs ESLint and stays cached until the manifests change, and a `js-lint` stage runs it. `script/lint` builds `js-lint`, so `make lint` and `make check` fail on a violation, and the image build depends on it as on the repo's other checks. ESLint, node and yarn are not prerequisites, and `make lint` never uses a host copy. Model: opus-5-5
31 lines
1005 B
Plaintext
31 lines
1005 B
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; a host copy would overwrite it at the
|
|
# js-lint stage's `COPY . .`.
|
|
node_modules/
|
|
.env
|
|
.env.*
|
|
*.db
|
|
*.sqlite
|
|
*.sqlite3
|
|
.DS_Store
|
|
.idea/
|
|
.vscode/
|
|
tmp/
|
|
temp/
|