e-volv

Planning playbook

Multi-RepoChangePropagation

Label a ticket `fleet-change` and the playbook applies the change across an explicit set of repositories.

Describe a change once in a ticket labelled `fleet-change` and the playbook applies it across every repository in a named set — one pull request per repository, each adapted to that repository's actual code.

Identifier
multi-repo-propagation
Version
1.0.0
Steps
3
Triggers
1
  • fleet
  • multi-repo
  • change-propagation
  • automated

When it runs

Ticketticket.labeled
Settle delay
30s after the event

Only when all hold

  • ticket.addedLabel equals fleet-change

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
    fleet-change Ticket Labelledtrigger

    The event that starts the run.

  2. 02
    Identify Target Repositoriesrepo.identify

    Resolves the event to a registered repository.

  3. 03
    Coordinate Fleet Changeagent.session

    A coordinator delegates to specialist agents.

The agent

Fleet Change Coordinator

Base type
Senior Developer
Temperature
0.2
Max iterations
40
Tools
5

Tickets · 3

  • read_ticketRead Ticket · read
  • read_ticket_commentsRead Ticket Comments · read
  • add_comment_to_ticketAdd Comment to Ticket · write

Git provider · 1

  • list_pull_requestsList Pull Requests · read

Status · 1

  • update_statusUpdate Status · write