change the backport label #10463
Open
change the backport label #10463
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
geekosaur
force-pushed
the
backport-label
branch
from
7af6139
to
3297f4a
Compare
ulysses4ever
approved these changes
Oct 15, 2024
By request in Matrix. If anyone else has an opinion, speak now or forever hold your peace! ☺ The new label is `Backport #NNN: title` which with GitHub's prefix and suffix for email is `[haskell/cabal] Backport #NNN: title (PR #MMM)`
geekosaur
force-pushed
the
backport-label
branch
from
3297f4a
to
b782c62
Compare
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.
By request in Matrix. If anyone else has an opinion, speak now or forever hold your peace! ☺
The new format is
Backport #NNN: title, which with GitHub's addenda (which can't be changed) will beTemplate B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR:
[ ] Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).(Mergify only reads this file onmaster.)