Ship on a go-ahead

Partly works today

A builder role writes the change and opens a pull request. Your Chief of Staff gives the go-ahead. Then the release runs itself: the database change, then the deploy.

Why it matters to you

Today the builder stops at the pull request. You open a terminal, paste a release script and watch it run. You are the last step of every change.

With this, the change goes live while you are on the school run.

How it works

  1. The builder ships the PR. A card assigned to @timebreez-builder ends with a branch and a pull request, noted on the card.
  2. The card asks for a go-ahead. Anything that touches production is flagged as needing one. Workers cannot approve their own work.
  3. The Chief gives the go-ahead. It checks the change against your mission and Never rules. You can give it yourself instead.
  4. CI applies it. Partly works today For HeyStax itself, the release job is built: each merge gets a plan, and it applies only when the owner runs it. For your own products, this will come later.
  5. The card closes with proof. Planned The release job will note what went live and when, on the same card.
Builder@timebreez-builder Pull requestnoted on the card Chief of Staffgo-ahead CI releasedatabase, then deploy Planned Card donewhat went live, when Planned 14:02@timebreez-builderPR opened 14:09@chief-of-staffgo-ahead given 14:15releaselive in production
The builder ships a pull request and notes it on the card. The Chief of Staff gives the go-ahead. The CI release and the closing note are planned: today you still run the release yourself.

A Tuesday with Bob

Bob runs a small payroll product. At 13:40 he tells his Chief, “staff need to see their leave balance on the payslip.”

The Chief adds a card for @timebreez-builder. The builder writes the change, with a new database column, and opens a pull request by 14:02. The card asks for a go-ahead because it touches production.

The Chief checks it against “never touch a closed pay period” and gives the go-ahead at 14:09. Today Bob still runs the release himself.

What stays yours

  • Who can give the go-ahead. Only you, or a Chief you granted go_ahead. Never the worker that did the work.
  • The Never rules. The Chief checks every go-ahead against them.
  • Turning it off. Take go_ahead back from the Chief and every release waits for you again.

Coming next

Planned Deploy on merge for your own products, such as Timebreez. A release that fails will stop, put the error on the card and message you.

Now you can hand a change to a role and see it reach production, with every step signed on the card.

Read next: Connect a worker to a role · Roles, workers and their keys


HeyStax Help © Hulupeep