sneak
eed24ff29c
check / check (push) Successful in 3m27s
The css-check stage splits both stylesheets after each "}" and prints their diff, so a failure names the rules that differ instead of a character position. The check workflow's fingerprint comment and build step name now include the stylesheet check, as the README does. The README's Stylesheet section names internal/handlers/recent_events.go among the files to edit. Model: opus-5-5
38 lines
1.4 KiB
YAML
38 lines
1.4 KiB
YAML
name: check
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- '**'
|
|
|
|
jobs:
|
|
check:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 2024-10-23
|
|
with:
|
|
# The superseded-status step needs history to walk ancestors (it
|
|
# aborts on a shallow clone).
|
|
fetch-depth: 0
|
|
|
|
- name: Mark superseded run statuses
|
|
# Gitea cancels the in-flight run when another commit is pushed to the
|
|
# same branch and records the cancellation as `failure`, so a commit
|
|
# that was never tested reads as a test result. The script rewrites
|
|
# those statuses to say what happened. See its header for why the
|
|
# state stays `failure` and not `skipped`.
|
|
env:
|
|
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
|
|
run: script/ci-mark-superseded
|
|
|
|
- name: Fingerprint the build context
|
|
# Writes the hash of the commit being checked into the context, which
|
|
# invalidates the `COPY . .` layer of every check stage: a commit
|
|
# that was never linted, format-checked, stylesheet-checked, tested
|
|
# and built cannot report success from cache.
|
|
run: git rev-parse HEAD > .ci-fingerprint
|
|
|
|
- name: Build Docker image (runs make fmt-check, golangci-lint, the stylesheet check, make test, make build)
|
|
run: script/cibuild
|