commitops

Get started

Your first ledger in ten minutes

About 10 minutes

Connect one mailbox, keep the candidates that are real, and link one repository, so you see what your team promised and whether it shipped.

Transcript, 30 seconds

CommitOps keeps a ledger of every promise your team made to a customer.

Name your workspace and list your domains, then connect one mailbox.

Candidates arrive in the inbox, each with the sentence it came from.

Keep the real ones, then connect GitHub or Linear to link the work.

Open the ledger: late promises first, ranked by the deals they block.

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

Before you start

  • A Google Workspace or Microsoft 365 mailbox you send customer mail from
  • Admin rights on one GitHub organization, Linear workspace, Jira site or GitLab group

Steps

  1. Name the workspace. Open Setup in the sidebar footer. The first step is Name the workspace and its domains; press List your domain, so mail between your own people is never read as a promise.
  2. Connect mail. Press Connect mail, then Connect beside Read Gmail or Read Outlook mail. We read 90 days of threads that have someone outside your company on them.
  3. Keep or discard five candidates. Press Open the inbox. Each candidate shows the exact sentence it came from. Press Keep when it is a real promise and Not a commitment when it is not.
  4. Connect a tracker. Press Connect a tracker and install GitHub, or connect Linear, Jira or GitLab. A pull request whose body says Satisfies C-142 links itself to that promise.
    Satisfies C-142
  5. Open the ledger. Once Setup shows 5 of 5, press Open the ledger. Late promises sort to the top, by the money they hold up.

What success looks like

  • Setup shows 5 of 5 required and the sidebar footer stops counting
  • The ledger lists the promises you kept, each with its quote
  • At least one promise shows a linked pull request or issue

Troubleshooting

The inbox is still empty after ten minutes
Only threads with someone outside your listed domains are read. Check Connect for first read in progress, and check that the mailbox writes to customers.
A pull request did not link
The body or title needs a keyword before the ref, such as Satisfies C-142, Closes C-142 or Fixes C-142. The ref alone does not link.
A step will not tick after you press its button
A click never marks a step done. The step ticks when the data is there, such as five decided candidates or one connected tracker.
Connect Gmail or OutlookGive CommitOps read access to one mailbox and its calendar, see exactly what it reads, and know what disconnecting deletes.3 minutesKeep or discard a candidateDecide whether a sentence is a real promise: keep it, edit it first, or discard it with a reason that teaches the queue.2 minutesRead 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 minutes