Repository navigation
ci(v10): Assign Junior backport PRs to the original author - #25529
Merged
Merged
Conversation
Co-Authored-By: Jan VamPeer Stöcklmair <jan.peer@sentry.io>
Member
|
Not a big fan of inline JS, but I think that is ok for that amount of code |
Contributor
size-limit report 📦
|
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
2 participants
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.
The Junior automation that backports
fixPRs to v10 now opens them without an assignee. This workflow fills that in: it reads theBackport of: #<number>line from the backport PR and assigns the original PR's author. For external PRs, it assigns the person who merged it instead.This targets
v10rather thandevelopon purpose.pull_request_targetruns the workflow file from the PR's base branch, so it only fires if the file exists onv10."External" uses the same
author_associationcheck aslabel-external-prs.yml, and bot authors fall back to the merger too. The workflow only runs when the PR has no assignees. It also listens toedited, so it still catches a backport whose body gets the reference after the PR is opened. A manual assignee is never overwritten.via Jan Peer Stöcklmair.
--
View Junior Session [Sentry]