Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce checks for dependent PRs #290

Open
gastaldi opened this issue Nov 9, 2022 · 1 comment
Open

Introduce checks for dependent PRs #290

gastaldi opened this issue Nov 9, 2022 · 1 comment
Labels
good first issue Good for newcomers

Comments

@gastaldi
Copy link
Contributor

gastaldi commented Nov 9, 2022

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

image

See: https://github.com/marketplace/dpulls
@gsmet
Copy link
Member

gsmet commented Nov 9, 2022

Is it really a problem in practice? I can recall a few cases but it doesn't happen that often IMO.

Anyway, it could be a good first issue.

@gsmet gsmet added the good first issue Good for newcomers label Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gastaldi @gsmet