-
Notifications
You must be signed in to change notification settings - Fork 407
Set up /backport action command #9800
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.
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
Set up /backport action command #9800
Conversation
Co-authored-by: LittleLittleCloud <[email protected]>
Co-authored-by: LittleLittleCloud <[email protected]>
- Write | ||
- Admin | ||
then: | ||
- backportPullRequest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is this command comes from
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The backportPullRequest
command was part of the GitOps.PullRequestIssueManagement schema that I initially added to resourceManagement.yml. However, I've now reverted that approach.
Instead, the implementation now uses a GitHub Actions workflow (backport.yaml) that calls the standard dotnet/arcade backport workflow, which is a more established and reliable approach used across dotnet repositories. (7e7adfc)
@copilot revert all other changes eexcept the backport.yaml |
…backport.yaml Co-authored-by: LittleLittleCloud <[email protected]>
Keep the change in Contributing.md |
pr_description_template: | | ||
Backport of #%source_pr_number% to %target_branch% | ||
/cc %cc_users% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonder if we could include a link to the comment that requested this. Could be useful to have that context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot do what Drew suggested
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a link to the requesting comment in the backport PR description template using %source_pr_url%#issuecomment-%trigger_comment_id%
. (Latest commit)
…t PR template Co-authored-by: LittleLittleCloud <[email protected]>
Restored the CONTRIBUTING.md documentation that explains how to use the |
Summary
This PR implements the
/backport
action command to automate the process of backporting merged pull requests to release branches.Changes
GitHub Actions Workflow
Added a GitHub Actions workflow in
.github/workflows/backport.yaml
that:dotnet/arcade/.github/workflows/backport-base.yml@main
workflow/backport to <branch-name>
commandsDocumentation
Added a "Backporting Changes" section to
CONTRIBUTING.md
that:/backport to <branch-name>
commandUsage
Contributors can backport changes by commenting on a merged PR:
This will automatically create a new pull request targeting the
dev17.13.x
branch with the changes from the original PR. The backport PR will include a link back to the original comment that requested the backport.Benefits
Fixes #9799
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.