Approvals, retries and reverts

Most tickets never need you after you press Start. This page covers the ones that do: how the verdict is decided, how a change is held for your approval, and the buttons on a ticket page for retrying, skipping, rejecting and reverting.

The verdict

When a run ends, the ticket page shows the verdict: a short summary, and for every acceptance criterion whether it is done, with the file and lines that show it. A change ships only when all of this agrees:

• every check passed (your build, lint, type check and tests, and the built-in checks)
• the review found file-and-line evidence for every required criterion
• the independent verifier, which never saw how the change was made, reached the same conclusion

A criterion without evidence is not done, and a failing check vetoes the change whatever the review says. If anything falls short after the fix rounds, nothing is committed: the ticket goes to Needs review with a report of what was tried and why it stopped.

Held changes

You can ask Reqursor Development to stop before it commits and wait for you. In Settings → Projects & repository, under Approval before commit, choose one or more of these:

• Hold every change for approval
• Hold changes that touch these paths
• Hold changes larger than (lines)

A change that is otherwise ready to ship, but matches one of these, is held instead of committed. The ticket moves to Needs review and the ticket page says a change is held for you. Your change is kept safe until you decide. A person whose role may approve runs sees two buttons:

• Approve & commit commits exactly the change that was held, without running the agent again. If the held change is gone or has changed since, the approval is dropped and the ticket runs again and is held again.
• Reject does not commit the held change. You can add a note.

Retry with hint

On a ticket in Needs review, Failed or cancelled, Retry with hint queues the ticket again with a note from you to the agent, for example "the config loader lives in src/config/load.ts". A hint that points at what went wrong is the fastest way to a good result. The retry reuses the ticket's branch.

Editing the ticket, for instance to sharpen an ambiguous criterion, and sending it back to Ready works too.

Skip

Skip sets a ticket in Needs review aside. The ticket is marked failed and will not run again unless you retry it. A change that is held for approval has Approve & commit and Reject instead of Skip.

Revert

If a shipped change turns out to be wrong, press Revert on the shipped ticket. It adds a revert commit on the ticket's branch. History is never rewritten. Reverting needs a role that may approve runs.

Pull requests

When the project opens pull requests, a shipped ticket shows View pull request. If it has a branch but no pull request yet, press Open PR. Pushing and pull requests are off until you turn them on: see Connect a repository.

The run report

Every run keeps a report of exactly what happened, pass or fail: the stages, the checks, the verdict, the cost and the time. Press Download Run Report on the ticket page.

• The board and ticket statusesWhat Needs review, Paused and the other states mean.
• Auto-detected checksThe checks that can veto a change.
• Roles and accessWho may approve, retry and revert.