This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
CI: automatically add a warning comment to PRs with backport labels #34132
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
jstarry
force-pushed
the
ci/backport-comment
branch
from
c22d912 to
1406c96
Compare
t-nelson
reviewed
Nov 17, 2023
Co-authored-by: Trent Nelson <[email protected]>
Co-authored-by: Trent Nelson <[email protected]>
t-nelson
approved these changes
Nov 17, 2023
|
Hope it works |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
Core contributors are not all aligned and informed on what is acceptable to backport to stable and beta branches
Summary of Changes
Add a mergify action that will add a comment whenever a PR is labeled a
v1.16orv1.17label. This extra comment will remind contributors and reviewers what the guidelines for backports are.Fixes #