Overrides and audit
Every way to override a review or skip one, who can use it, where it's recorded, and what carries over to the next push.
An override changes what Axon Shaft does on a pull request. None of them changes a past run: a run's page keeps the card it had, and each commit keeps its own check runs.
The ways to override
| Override | Who can use it | What it does | Recorded in | Carries over to the next push |
|---|---|---|---|---|
/review | Write access | Reviews a pull request that an event setting, the forks setting, a filter or a skip label held back. | GitHub: the comment | No: the next push follows the settings again |
| A skip label | Anyone GitHub lets add labels | Skips reviews on pull request events. | GitHub: the label event | Yes, until the label is removed |
| Resolving an inline thread | Anyone who can resolve threads on GitHub | Closes the thread. The finding isn't posted again inline, but the next review still lists it in the summary if it still finds it. | GitHub | Yes |
| Settings and automations on the dashboard | The account's admin, or the Admin or Maintain role on the repo | Changes what every later run does: checklists, filters, gates, rules, model and the rest. | The audit log | Yes |
| Pausing the project | The account's admin, or the Admin or Maintain role on the repo | Stops every run on the repo, commands included. | The audit log | Yes, until it's resumed |
| Turning a checklist off | The account's admin, or the Admin or Maintain role on the repo | Its chip shows ➖ and it posts no check run. | The audit log | Yes |
Commands from someone without write access start nothing, and axonshaft[bot]'s own comments and other bots' comments never start a run.
An override isn't an ignore
/review and the skip settings decide whether a review runs. They don't hide a finding. When a review runs, it reports what it finds, and a finding stays in the summary comment until a review finds it fixed.
There's no way to dismiss one finding so that later reviews leave it out. To stop one kind of finding on a project, turn off its checklist, or add a review rule on the dashboard that says what not to flag.
The audit log
The audit log records every change made on the dashboard: projects added, removed, paused and resumed, automations added, changed, reset and removed, Claude tokens saved and deleted, settings changed, and workflow files added or updated. Each entry names who made it, the project and the fields that changed, never the values. The account's admin reads it in the account's settings. Entries are kept for 3 months. See Audit log.
Past runs
- A run's page keeps the card, findings and reply it had, for 7 days. The workflow run stays on GitHub.
- The summary comment on the pull request shows only the latest review, since each push edits it.
- Each commit keeps the check runs its review posted. A later push posts new ones on the new commit and doesn't change the old ones.
Last updated on