Axon Shaft docs

Troubleshooting

Why a pull request wasn't reviewed, a required check that never finishes, a command that did nothing, and other problems, each with its cause and fix.

Start with the pull request's Checks tab, or the repo's Actions tab, and find the Axon Shaft job. What it shows tells you which section below applies. Every code a run shows has its own section on Failure, notice and skip codes.

Why wasn't my pull request reviewed?

There's no Axon Shaft job

CauseFix
The workflow file isn't on the pull request's base branch. On pull_request_target, GitHub runs the workflow from the base branch, so a workflow added only in the pull request doesn't run.Merge the workflow into the default branch first. The project's Overview shows an Add the workflow card until it's there.
The workflow doesn't list the event, such as ready_for_review.Compare it with the workflow file. The Overview shows a Workflow needs an update card that lists what's different.
A skip label was removed, or a setting changed. The workflow doesn't run on labeled, and settings don't start runs.Push, or comment /review.

The job failed

The step's message says what to do, and the job summary shows a card with the code. The common ones on a first run:

Later on: rate_limited, review_timed_out, review_failed and api_error.

The job passed and posted nothing

The run ended with a notice, which the job's annotations show. The notice says which:

NoticeCauseFix
skip_labelThe pull request has a skip label.Remove it and push, or comment /review.
filteredIt's from a bot, an outside contributor or Axon Shaft, or into a branch the Code review doesn't cover.Change the filter in the Code review automation, or comment /review.
pausedThe project is paused.Resume it in the project's Settings.
spending_capThe month's runs reached the monthly cap.Wait for the 1st (UTC), or have the account's admin raise the cap.
pull_request_limitThe pull request started 10 /ask and /fix runs this hour.Wait for the next hour, then comment again.
fork_pull_requestA fork's pull request on a workflow that runs on pull_request.Run the workflow on pull_request_target.
No code: Code review is off, or the event isn't one of its When it runs choices.The automation's settings.Turn it on, or add the event, in the Code review automation.
No code: a fork's pull request the forks setting holds back.The forks setting.Comment /review, or change the setting.

A run with dry_run: true prints the review to the job log and posts nothing. Remove the input.

It reviewed, but with another automation's checklists

Only the first review automation that's on runs, in the Automations tab's order. Turn the other off, or move the one you want first.

A required check never finishes

CauseFix
The run posted nothing, so it posted no check runs: the pull request was skipped, the project is paused, or the cap was reached.See The job passed and posted nothing. For a skipped pull request, comment /review.
The required checklist is turned off in the automation. A turned-off checklist posts no check run.Turn it back on, or remove it from the required checks.
The required check is Axon Shaft / rules, which an action before 1.6 posts only when the project's own checks found something.Require the checklists' own check runs instead.
The installation hasn't approved Checks (write). The job log warns about it.The account's admin approves it on GitHub. See Permissions to review.
The pull request is in a merge queue. The workflow doesn't run on merge_group.Don't require Axon Shaft's checks in the merge queue's rules.

A checklist whose files the pull request doesn't touch posts skipped, which GitHub counts as passing.

A command did nothing

What you seeCauseFix
No reaction, and the job was skipped or logged nothingThe command isn't at the start of a line, or it's in a quote or code.Put it at the start of a line. See What counts as a command.
No reaction, and the job ended with no_write_accessThe commenter has no write access.Ask someone with write access.
😕, with a notice that the request was refused/fix or /axonshaft in a review or on a line of the diff.Comment it in the Conversation tab.
A failure card in the reply/fix couldn't run or push: push_failed, self_hosted_unsupported, credentials_in_checkout or sandbox_unavailable.Follow the code's fix.
/help posted nothing the second timeIt posts once for each set of settings.Change a setting, or scroll up to the first reply.

Wrong or unexpected results

What you seeCauseFix
A file wasn't reviewedIt matches the skip globs. The summary counts the files they left out.Change the skip globs.
A checklist shows ⬜No changed file matched its paths, or the model says it didn't do that check. "What this PR does" names it.Check the checklist's paths in the catalog.
The review ignores the repo's conventionsOnly the guide files on the base branch are read, cut at 8,000 characters each and 30,000 in all.Move the rules to the top of a guide file, or add them as review rules on the dashboard.
The same finding comes back after a fixThe review reads the head commit, so the fix wasn't in it, or the model judged it still open.Push the fix. A later review that finds it fixed resolves the thread.
A finding names a vulnerability in a package you didn't changeThe lockfile changed that package's version, directly or as a dependency.Check the lockfile's diff at the line the finding gives.
The run used a smaller model than expectedThe Claude plan couldn't use the model auto picked. The footer's table has a Fallback row.Set the model on the dashboard, or use a plan that has it.

Known vulnerabilities didn't run

CauseFix
The pull request changes no lockfile the checklist runs on.The Known vulnerabilities page lists them. A lockfile that isn't listed isn't read.
The lockfile is listed, but its script doesn't read it yet.The page's Lockfiles it reads table says which ones the script reads.
The packages are scoped, private, from git or a URL, or the repo sets another registry.These are never sent. See Package lookups.
osv.dev and GitHub's advisory database both failed, or the API refused the lookup.The checklist is skipped with the reason, and never passes. Re-run the job.

Rate limits

The run failed with rate_limited. The repo called the API too often, for example many comments at once. Wait the seconds the message gives and re-run the job. Limits has the numbers.

Last updated on