Skip to content

Cap what a single fork pull request can spend #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gvonnessi merged 1 commit into from
Aug 20, 2026
Merged

Cap what a single fork pull request can spend #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,24 @@ on:
branches: [main]
pull_request:

concurrency:
# A new push to the same PR or branch supersedes the run in flight. Without
# this every push queued a *fresh* full set of jobs alongside the old ones,
# so a branch pushed five times held five complete matrices at once — on
# paid Blacksmith runners, and with nothing reclaiming the superseded work.
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true

jobs:
check:
name: fmt + clippy + test (${{ matrix.os }})
runs-on: ${{ matrix.os }}
# Capped because the GitHub default is **six hours** per job, and this
# workflow is reachable from a fork pull request. Measured over the last
# six runs the slowest job here is 2m07s, so 20 minutes is roughly 9x
# headroom while removing the runaway: a stuck or hostile job now costs
# 20 minutes of a paid runner rather than a working day of one.
timeout-minutes: 20
strategy:
fail-fast: false
matrix:
Expand Down
Loading