commitops

Daily use

Connecting the PR to the promise

About 4 minutes

Point a pull request or issue at the promise it keeps, confirm the links CommitOps proposes, and read the comment it leaves on the PR.

Transcript, 30 seconds

Every kept promise has a ref, such as C-142.

Write Satisfies C-142 in the pull request, and the link is made at once.

Work that only looks similar is proposed, and a person confirms it.

Nothing below 0.90 links itself.

The PR comment shows engineers the account and the deal waiting on it.

Captions on by default. Made from this page’s steps, with demo data only.

Before you start

  • A kept promise on the ledger, with its ref such as C-142
  • GitHub, Linear, Jira or GitLab connected on Connect

Steps

  1. Find the ref. Every kept promise has a ref, shown on the ledger and at the top of its page. Give the ref to whoever builds it.
  2. Write the keyword. Put Satisfies C-142 in the title or body of the pull request or issue. Closes C-142 and Fixes C-142 work too, in any case. The link is made at once with confidence 1.00.
    Satisfies C-142
  3. Or share a roadmap slug. A GitHub or Linear label named roadmap:<slug>, or a Linear project of that name, links work to a promise carrying the same slug, set with the set_roadmap_slug tool. It links at 0.90.
  4. Confirm a proposal. Work that only looks similar is proposed, never linked. On the promise page, under Proposed, waiting on a person, press Link it or Not this.
  5. Link by hand. In the Work panel, type a key such as ENG-284 or owner/repo#42 under Link a pull request or issue, and press Link work. Press Unlink to take a link off.
  6. Read the PR comment. On a private repository the comment names the promise, the account, the due date and the deal money it holds up. On a public one it names the ref only. Reply not this one to unlink.

What success looks like

  • The promise page lists the pull request or issue in its Work panel
  • When the work merges, the promise shows a dated check that it was met
  • A GitHub pull request carries one CommitOps comment naming the ref, unless your workspace turned comments off

Troubleshooting

The keyword did not link
The ref needs a keyword before it, such as Satisfies C-142, and must name a kept promise in this workspace. A candidate still in the inbox does not link.
A proposal you rejected never comes back
That is on purpose. A pair a person unlinked or rejected is never linked again by a pass. Link it by hand if you change your mind.
The comment shows only the ref
The repository is public, or GitHub did not answer whether it is private. A public pull request never shows a title, an account or money.
Read the ledgerFind any kept promise, filter to what is late or blocking, and open one to link work, move its date or withdraw it.4 minutesRead the gapsAct on the two lists that cost money: promises with no work started, and work that shipped without anyone telling the customer.5 minutesTell the customer it shippedTurn merged work into a draft in your own Gmail, checked against the code, and let the told sweep notice when the news went out.3 minutes