A push that only changed Cargo.lock failed to create any Actions run while the concurrency group was present; removing it restores reliable push triggering. Single-dev CI doesn't need run-cancellation. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
43 lines
975 B
YAML
43 lines
975 B
YAML
name: CI
|
|
|
|
# Runs on the self-hosted host-mode runner on the desktop (label `arch`). The
|
|
# gitbutter VPS only queues the job; all compile/test compute happens locally.
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
pull_request:
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
check:
|
|
runs-on: arch
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Toolchain versions
|
|
run: |
|
|
rustc --version
|
|
cargo --version
|
|
cargo clippy --version
|
|
cargo deny --version
|
|
cargo audit --version
|
|
|
|
- name: Format check
|
|
run: cargo fmt --all -- --check
|
|
|
|
- name: Clippy (all targets, warnings as errors)
|
|
run: cargo clippy --all-targets -- -D warnings
|
|
|
|
- name: Tests
|
|
run: cargo test --all-targets
|
|
|
|
- name: Doc tests
|
|
run: cargo test --doc
|
|
|
|
- name: cargo-deny (advisories, bans, licenses, sources)
|
|
run: cargo deny check
|
|
|
|
- name: cargo-audit
|
|
run: cargo audit
|