Pull requests, approvals, and merge

The last step — getting a session’s work toward your main branch — follows your normal process. Code reaches the main branch only through a pull request and your approval policy, never directly from a session.

Open a pull request

chronos session pr <id>

This opens a pull request for the session’s branch, following your team’s workflow. In the dashboard, Create PR does the same and shows you the link.

Approve

chronos session approve <id>

Approving certifies a session’s work. It requires the right permission — your organization decides who can approve. In the dashboard, Approve records it.

Merge — only by policy

chronos session merge <id>

A merge proceeds only when all of these are true:

1. Checks are green — see Reviewing changes.
2. The required approvals are in place.
3. The person merging has permission to merge.

If anything is missing, the merge is blocked and Chronos tells you exactly why. There is no way to bypass this.

   checks green ──┐
   approvals    ──┼──▶  has merge permission ? ──▶  MERGE
   (required)     │              │
                  └── any missing ┴──▶ BLOCKED (reasons shown)

Defense in depth

Chronos enforces your policy, and we recommend pairing it with your repository host’s own branch protection so the two reinforce each other.

Everything is recorded

Every pull request, approval, and merge is recorded with who did it and when, along with the checks it passed — so you can always answer “who approved this, and against what”. The records land in the append-only audit log alongside every other session action.

After merge

A merged session is cleaned up like any other — its branch and working copy are removed, with nothing left behind.