Repository navigation
Assign merged pull requests to the release milestone - #327
Merged
Merged
Conversation
slachiewicz
force-pushed
the
agent/pr-automation
branch
from
October 11, 2026 22:01
e81dfdf to
1b904bf
Compare
slachiewicz
marked this pull request as ready for review
October 11, 2026 22:40
This file contains hidden or 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
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.
Part of mojohaus/.github#15. Adds the shared PR automation that mojohaus/versions, license-maven-plugin and flatten-maven-plugin use: a merged pull request goes into the open milestone of its branch, here 2.0.1, unless it is labelled
skip-changelog. When more than one milestone is open, the one whose description saysbranch: masteris used.