CI is far too tedious
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
A PR that is approved and passes the CI can take days to merge. If other PRs cut the queue and get merged while the CI is rebuilding things for the $n$-th time, the PR needs to manually be inspected for the $n+1$-th iteration of merging main and re-running everything from scratch. This is wasteful of time and wasteful of resources. Occasionally all PRs become blocked when resource limits are exceeded. Worse, there seems to be little reason for it. If the changes are tested and pass the tests and do not conflict with merges that keep cutting the queue, then they could just be merged into main without rerunning all the tasks for the $n+2$-th time.
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
The issue names no files, tests, or entry points. Start by examining the repository's CI and merge configuration and reproduce the repeated rebuild and queue behavior. Done means approved, passing pull requests can merge without unnecessary full reruns while preserving conflict and test safety.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100