quarkusio / quarkusio/quarkus-github-bot
Introduce checks for dependent PRs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 30
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
When a large PR is split into smaller chain of dependent PRs or if it is common for you to have a single change that spans several other pull requests spread out across multiple projects, and if the order in which they are merged is significant, it would be nice if Quarkus bot checked that to prevent accidental merges
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
No files, tests, or entry points are identified in the issue. Start by reviewing the bot's existing pull-request checks and comparing the desired dependent-PR behavior with the linked dpulls project; done means detecting merge-order dependencies and preventing accidental merges when they are unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100