Approving and shipping
Draft and ready-for-review pull requests
Novix always opens a pull request. Five conditions decide whether it lands ready for review or as a draft.
Novix opens a pull request on every drafted fix, so nothing waits on somebody visiting the dashboard. What is decided automatically is only whether it arrives ready for review or as a draft.
The five conditions for ready for review
All five, or it opens as a draft.
- The fix review passed.
- The fix review actually ran. A review that could not complete is not a review that passed.
- The risk rating is low.
- The verdict is a bug, not a requested change.
- The workspace is inside its spend cap.
Anything else opens as a draft carrying the reason, in the audit log and on the task’s trace. You are never left guessing why.
If you would rather it opened nothing
Set review to required in settings and Novix opens nothing at all. The drafted fix waits in the dashboard and a person opens the pull request.
After the pull request opens
Novix watches your CI. It never becomes it. It reads what your own pipeline posted on the head commit and shows it on the task, along with a preview URL when one of your deploy bots published one. A result it could not fully read is shown as unreadable, with the reason, never as a pass.
When your CI goes red on a GitHub pull request, Novix drafts its patch again and pushes one repair commit to the same branch, for that failure only. A fix that comes back as a change to a workflow file is refused and handed to a person.