melange/update block: provide config option to indicate that automated pull requests should be merged in order rather than superseding and closing previous unmerged PRs #1681
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d pull requests should be merged in order rather than superseding and closing previous unmerged PRs Some packages such as [jenkins](https://github.com/wolfi-dev/os/blob/main/jenkins.yaml) are required to build all upstream versions. The default behaviour of the update bot will close previous automated update bot PRs superceeded by a new version. This new config option will allow maintainers to tell the update bot to _not_ close existing PRs if they have not yet been merged. Signed-off-by: James Rawlings <jrawlings@chainguard.dev>
hectorj2f
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some packages such as jenkins are required to build all upstream versions. The default behaviour of the update bot will close previous automated update bot PRs superceeded by a new version.
This new config option will allow maintainers to tell the update bot to not close existing PRs if they have not yet been merged.
This will allow the bot to create issues like this...
And not close old PRs.
The new config looks like