Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

github-actions: support for copying the backport labels #42266

Merged
merged 3 commits into from
Jan 9, 2025
Merged

github-actions: support for copying the backport labels #42266

merged 3 commits into from
Jan 9, 2025

Conversation

v1v
Copy link
Member

@v1v v1v commented Jan 8, 2025 •
edited
Loading

Proposed commit message

Trying to solve the below statement:

Currently all merges will have the needs_team label, so trying to find non-triaged PR's gets a bit bloated

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Requires elastic/oblt-actions#207

Use cases

Screenshots

Logs

@v1v v1v added backport-7.17 Automated backport to the 7.17 branch with mergify backport-8.x Automated backport to the 8.x branch with mergify backport-8.17 Automated backport with mergify labels Jan 8, 2025
@v1v v1v self-assigned this Jan 8, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 8, 2025
@v1v v1v marked this pull request as ready for review January 9, 2025 12:49
@v1v v1v requested a review from a team as a code owner January 9, 2025 12:49
@v1v v1v added backport-skip Skip notification from the automated backport with mergify and removed needs_team Indicates that the issue/PR needs a Team:* label backport-7.17 Automated backport to the 7.17 branch with mergify backport-8.x Automated backport to the 8.x branch with mergify backport-8.17 Automated backport with mergify labels Jan 9, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 9, 2025
@v1v v1v added the backport-8.x Automated backport to the 8.x branch with mergify label Jan 9, 2025
@v1v v1v merged commit 3f1bc1e into elastic:main Jan 9, 2025
9 checks passed
mergify bot pushed a commit that referenced this pull request Jan 9, 2025
@v1v @mergify
github-actions: support for copying the backport labels (#42266)
66b99ed 
(cherry picked from commit 3f1bc1e)
@mergify mergify bot mentioned this pull request Jan 9, 2025
Merged
6 tasks
v1v pushed a commit that referenced this pull request Jan 9, 2025
@mergify
github-actions: support for copying the backport labels (#42266) (#42279
5c94629 
)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexsapran alexsapran alexsapran approved these changes

Assignees

@v1v v1v

Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-skip Skip notification from the automated backport with mergify needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@v1v @alexsapran