Skip to content

ci: Actions cost controls - #1

Open
hedgerow-dev wants to merge 2 commits into
mainfrom
chore/ci-cost-controls
Open

hedgerow-dev wants to merge 2 commits into
mainfrom
chore/ci-cost-controls

Conversation

@hedgerow-dev

Copy link
Copy Markdown
Owner

Cuts private-repo Actions consumption, which was tracking to roughly 3,400 minutes against a 2,000 included allowance this month.

See the commit message for what changed in this repository and why.

🤖 Generated with Claude Code

kennethkcox and others added 2 commits August 14, 2026 20:59
Private-repo Actions minutes were tracking to roughly 3,400 against a
2,000 included allowance this month. Two changes here:

- concurrency groups so a new commit on a ref supersedes the in-flight
  run for that ref. Deploy, publish and release workflows get the group
  without cancel-in-progress: those serialize instead, because a
  half-finished publish is worse than a queued one.

- timeout-minutes on every job that had none. The GitHub default is 360
  minutes, so one hung job could eat a fifth of the monthly allowance.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CI was doing the job of a linter, with a multi-minute feedback loop and a
billed runner. Across the account the large majority of failed runs died
on formatting or lint, which a laptop settles in well under a second: on
briar, 25 of the last 25 CI failures were cargo fmt --check.

This hook runs the same fast checks before a push. It is opt-in per
clone, since core.hooksPath is local config and not something a commit
can set:

    git config core.hooksPath .githooks

Missing tools are skipped with a note rather than blocking the push, so
a clone without the dev environment is still usable, and
`git push --no-verify` bypasses it when that is what you want. Nothing
here replaces a CI gate: the matrix, the clean environment and the
required checks all stay where they are.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants