backported-labels workflow: run on stable-* watching for merges, add backported-* label to backported PRs #1025
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
himdel
added
backport-4.2
…backported-* label to backported PRs Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue
himdel
force-pushed
the
backported-labels
branch
from
b33ed1c to
ac05e9e
Compare
rochacbruno
approved these changes
Oct 14, 2021
Backport to stable-4.2: 💚 backport PR created✅ Backport PR branch: Backported as #1027 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Oct 14, 2021
…backported-* label to backported PRs (#1025) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue (cherry picked from commit 825086d)
Backport to stable-4.3: 💚 backport PR created✅ Backport PR branch: Backported as #1028 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Oct 14, 2021
…backported-* label to backported PRs (#1025) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue (cherry picked from commit 825086d)
Backport to stable-4.4: 💚 backport PR created✅ Backport PR branch: Backported as #1029 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Oct 14, 2021
…backported-* label to backported PRs (#1025) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue (cherry picked from commit 825086d)
newswangerd
pushed a commit
that referenced
this pull request
Oct 14, 2021
…backported-* label to backported PRs (#1025) (#1029) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue (cherry picked from commit 825086d) Co-authored-by: Martin Hradil <[email protected]>
github-actions
bot
added
the
backported-4.4
newswangerd
pushed a commit
that referenced
this pull request
Oct 19, 2021
…backported-* label to backported PRs (#1025) (#1027) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue (cherry picked from commit 825086d) Co-authored-by: Martin Hradil <[email protected]>
newswangerd
pushed a commit
that referenced
this pull request
Oct 19, 2021
…backported-* label to backported PRs (#1025) (#1028) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue (cherry picked from commit 825086d) Co-authored-by: Martin Hradil <[email protected]>
github-actions
bot
added
backported-4.2
jctanner
pushed a commit
to jctanner/galaxy_ng
that referenced
this pull request
Dec 1, 2021
…backported-* label to backported PRs (ansible#1025) Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch. It's watching for commit messages ending with `foo (ansible#123) (#456)`, and using the penultimate PR number, the format patchback uses. Identical to the UI version ( ansible/ansible-hub-ui#428 ) No-Issue
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.
Adding a workflow that updates a backported PR with a backported-* label once merged in a stable-* branch.
It's watching for commit messages ending with
foo (#123) (#456), and using the penultimate PR number, the format patchback uses.Identical to the UI version ( ansible/ansible-hub-ui#428 )
Cc @newswangerd