aio-libs / multidict / 35607225346

87%

push

github

Cancel superseded CI runs on pull requests (#1500)

<!-- Thank you for your contribution! -->

## What do these changes do?

Adds a `concurrency` group to the CI/CD workflow so that pushing a new
commit to a pull request cancels the still running or pending run for
the previous commit.

Pull request runs are grouped by PR number. Every other event (pushes to
`master` and release branches, tags, the merge queue, the daily
schedule) falls back to `github.run_id`, so each of those runs gets a
unique group and is never cancelled or replaced while pending. Grouping
those by `github.ref` with a conditional `cancel-in-progress` would not
be enough, since GitHub keeps only one pending run per group and
silently drops the older one.

## Are there changes in behavior for the user?

No, this only affects CI.

## Is it a substantial burden for the maintainers to support this?

No.

## Related issue number

N/A

## Checklist

- [x] I think the code is well written
- [ ] Unit tests for the changes exist: N/A, CI configuration only
- [ ] Documentation reflects the changes: N/A
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`: N/A
- [x] Add a new news fragment into the `CHANGES/` folder
- [x] `make doc-spelling` passes and any new technical words are added
to `docs/spelling_wordlist.txt`

Drafted with Claude Code (Claude Opus 5); reviewed by @asvetlov.

<details>
<summary>Agent run details (optional, for reviewers)</summary>

Lint: `pre-commit run --files .github/workflows/ci-cd.yml` passes
(workflow schema, timeout-minutes, yamllint).
Docs: `make doc-spelling` passes.
The cancellation behaviour itself can only be observed on GitHub
Actions; it was not exercised locally.
</details>

---------

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

762 of 1524 branches covered (50.0%)

Branch coverage included in aggregate %.

6455 of 6727 relevant lines covered (95.96%)

1.92 hits per line