Skip merge process if an existing PR exists and has the "hold" label
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 11
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 3
Description
Sometimes, we have to wait before synchronizing our downstream (for instance, there's a global merge freeze). There's no way to tell the bot to skip the update except disabling the GitHub action which is not very user-friendly because someone has to remember to enable it back.
It would be useful for the bot to check if a PR already exist and if it has the "hold" label (signalling that it needs to wait), it wouldn't try to update the PR.
Contributor guide
No contributing guide indexed for this repository
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 tracing the bot's existing PR update or merge flow and the GitHub Action entry point described in the issue. Check how an existing PR and its labels are read, then verify that a PR labeled "hold" is left unchanged while other existing PRs continue through synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100