e-volv

Review playbook

BackporttoReleaseBranch

Label a merged PR `backport/<version>` and the playbook opens a matching backport PR.

Label a merged pull request `backport/<version>` and the playbook applies the same change to the `release/<version>` branch and opens a backport PR against it.

Identifier
backport-to-release
Version
1.1.0
Steps
4
Triggers
1
  • backport
  • release
  • pull-request
  • automated

When it runs

Pull requestpull_request.labeled
Settle delay
10s after the event

Only when all hold

  • pullRequest.merged equals true
  • pullRequest.addedLabel starts with backport/
  • actor.username not contains [bot]

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    backport/* Label on Merged PRtrigger

    The event that starts the run.

  2. 02
    Clone Default Branchgit.clone

    Shallow-clones the repository at the right ref.

  3. 03
    Create Backport PRagent.run

    One agent works the task with its toolkit.

  4. 04
    Publish Backport Reportreport.publish

    Posts or updates a deduplicated report comment.

The agent

Backport Engineer

Base type
Senior Developer
Temperature
0.15
Max iterations
45
Tools
12

Git provider · 7

  • read_pull_requestRead Pull Request · read
  • get_pull_request_diffGet Pull Request Diff · read
  • list_pull_requestsList Pull Requests · read
  • create_branchCreate Branch · write
  • create_or_update_fileCreate or Update File · write
  • create_pull_requestCreate Pull Request · write
  • add_labelsAdd Labels · write

Filesystem · 2

  • read_fileRead File · read
  • list_dirList Directory · read

Code search · 1

  • code_searchCode Search · read

Terminal · 1

  • run_terminal_cmdRun Terminal Command · write

Status · 1

  • update_statusUpdate Status · write