Status Codes
Check out the main status codes you can come across in Aviator. If any issue or failure happens, you will see a status code or its corresponding description.
If Aviator runs in to any issues or failures, we will surface a status code or its corresponding description. Please refer to the table below.
NOT_APPROVED
101
PR does not have the required number of approvals.
READY_LABEL_REMOVED
104
Someone has removed the trigger label to dequeue the PR.
BLOCKED_BY_LABEL
105
Someone has manually added the failure label to block the PR.
MERGE_CONFLICT
106
There is a merge conflict.
FAILED_TESTS
107
One of more of the required CI status checks failed.
MISSING_OWNER_REVIEW
109
The PR does not have required reviews from the codeowners.
CI_TIMEDOUT
111
This is only reported if a CI timeout is specified in the merge rules. The PR's required CI status check did not complete in the specified time and will be dequeued.
STUCK_TIMEDOUT
112
The CI has already timed out, and the PR is still in a stuck state.
UNRESOLVED_CONVERSATIONS
113
The PR still has unresolved conversations. This is only applicable if conversation_resolution_required=true in merge rules.
DRAFT_PRS_UNSUPPORTED
114
Draft PRs are only supported with a GitHub Team plan, GitHub Enterprise, or GitHub Enterprise Cloud. See the GitHub Docs for more information.
UNVERIFIED_COMMITS
115
Not all commits in the PR have been signed/verified. This is applicable if your merge rules configuration requires verified commits.
COMMIT_ADDED
116
The PR is now stale because a new commit has been added since the CI has been run.
CHANGES_REQUESTED
117
There are changes requested on the PR.
UNSUPPORTED_BASE_BRANCH
118
We do not support merging into the specified base branch.
BLOCKED_BY_GITHUB
110
Blocked due to internal GitHub reasons.
FAILED_UNKNOWN
108
Failed due to an internal error.
MANUAL_RESET
300
Reset triggered manually.
RESET_BY_FAILURE
301
A reset was triggered due to failure of CI
RESET_BY_SKIP
302
A reset was triggered due to a new skip line PR
RESET_BY_DEQUEUE
303
A reset was triggered due to a PR being manually dequeued
RESET_BY_MANUALLY_CLOSED
304
A reset was triggered because a PR was manually closed
RESET_BY_FF_FAILURE
305
A reset was triggered because Aviator failed to fast forward
RESET_BY_CONFIG_CHANGE
307
A reset was triggered due to config change
RESET_BY_TIMEOUT
308
A reset was triggered due to timeout
RESET_BY_INVALID_PR_STATE
309
A reset was triggered since the queued PR is no longer ready to merge
RESET_BY_COMMIT_ADDED
310
A reset wsa triggered by addition of a new commit in a queued PR
Last updated
Was this helpful?