Skip to content

An unattended split builds every part without waiting for merges

Choose a tag to compare

View all tags
@mashware mashware released this 23 Oct 17:17
v0.100.0
1e33605
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

In short

  • publish --part … --stack when the orchestrator offers it. <cmd> ticket --json saying "stack": true means the orchestrator can stack a split's parts: ship passes --stack with every part, and the next part no longer waits for the previous one to merge.
  • /flow:work:run routes why = next. Nothing merged: the published parts stay published, meta.json.base becomes the part published last (or the umbrella), and the next startable MR/PR is built on it — a published dependency counts as met on this route only.
  • Without stack nothing changes: the next part waits for why = merged, as before.

Why
An unattended split used to stop after each part until a person merged it, so a split ticket left to run overnight was one part long in the morning. agent-runner v0.28.0 stacks a split's parts (mashware/agent-runner#481): each part's PR targets the part below it, and the orchestrator retargets and restacks on its own.

Upgrading
Nothing to configure. Only an orchestrator that says "stack": true changes anything.

Assets 2
Loading