Skip to content

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.

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

Merged
merged 6 commits into from
Oct 9, 2025
+37 −0
Merged

Set up /backport action command #9800

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
6a880d4
Initial plan
Copilot Sep 30, 2025
4580568
Add /backport action command to GitOps configuration
Copilot Sep 30, 2025
7e7adfc
Add backport documentation to CONTRIBUTING.md
Copilot Sep 30, 2025
b2cba6a
Add backport workflow for PRs
LittleLittleCloud Oct 7, 2025
2a4ade7
Revert CONTRIBUTING.md and resourceManagement.yml changes, keep only …
Copilot Oct 7, 2025
40817c2
Restore CONTRIBUTING.md documentation and add comment link to backpor…
Copilot Oct 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .github/policies/resourceManagement.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,21 @@
- cleanEmailReply
description: Email cleanser

- if:
- payloadType: Issue_Comment

Check failure on line 50 in .github/policies/resourceManagement.yml

View check run for this annotation

Dotnet Policy Service / GitOps/YmlValidation

.github/policies/resourceManagement.yml#L50 

Exception during deserialization. Unknown condition specified.
- commentContains:
pattern: '^/backport to '
isRegex: True
- isAction:
action: Created
- activitySenderHasPermissions:
permissions:
- Write
- Admin
then:
- backportPullRequest
Copy link
Member

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

Copy link
Contributor Author

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)

description: Backport PR to release branch when /backport command is used

- if:
- payloadType: Pull_Request
then:
Expand Down
16 changes: 16 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,22 @@ When you submit a pull request, a CLA-bot will automatically determine whether y

If you want to submit a feature or a substantial code contribution, please discuss it first with the the team by [filing an issue](https://github.com/dotnet/project-system/issues/new), making sure it follows our [Roadmap](docs/repo/roadmap.md).

## Backporting Changes

To backport a merged pull request to a release branch, add a comment to the PR with the following format:

```
/backport to <branch-name>
```

For example, to backport to the `dev17.13.x` branch:

```
/backport to dev17.13.x
```

The backport action will automatically create a new PR targeting the specified branch. This command is only available to users with Write or Admin permissions on the repository. Available release branches include `dev17.13.x`, `dev17.9.x`, `dev17.8.x`, `dev17.7.x`, `dev17.4.x`, and `dev16.11.x`.

For additional information, see the following:

- [Getting Started](docs/repo/getting-started.md)
Expand Down