"merge on green" for PRs like PyTorch core's "@pytorchbot merge -g"
Open
Nobody has claimed this yet.
module: ci
triaged
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 The feature, motivation and pitch
I frequently leave myself notes to come back to a PR after CI is done and merge it. It would be nice if we had a way to specify that a PR should be merged once CI comes back green, like PyTorch core does with @pytorchbot merge -g.
This issue should probably be in https://github.com/orgs/pytorch/projects/78 but I'll leave that decision to @mergennachin .
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
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 reviewing the linked PyTorch project 78 and the referenced @pytorchbot merge -g behavior. Define what repository workflow or entry point would own the request, then verify that a marked PR merges automatically after CI becomes green without a manual follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100