Concurrency bug: Multiple PR workflows run simultaneously, exhausting resources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
The GitHub Actions workflow has a concurrency configuration that's supposed to cancel previous runs when new commits are pushed to a PR, but it's not working. Instead, multiple workflows run simultaneously, exhausting disk space and other resources.
The cancel-in-progress condition
${{ github.ref != 'refs/heads/main' }}
isn't properly canceling PR workflows because: it isn't narrowed enough (likely not including the branch/PR identifier). Without a proper concurrency group key, GitHub can't match and cancel previous runs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub Actions workflow containing the concurrency configuration and inspect its group key and cancel-in-progress condition. Reproduce the behavior by pushing successive commits to a pull request, then verify that the earlier workflow is cancelled and resources are no longer exhausted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100