Approving and shipping
Merging the pull request is the approval
Approve where you already are, or just merge. Novix never merges on its own, from any path.
There is no separate approval step to remember. Merging the pull request with your own repository access is itself the approval, recorded and attributed to the account that merged it.
Approving without leaving the doorway
novix approve
On Linear, Jira, Asana, ClickUp, monday, Notion and the six help desks, that comment merges. So does the approve and deploy button in a Slack thread, and a reply to a Novix email.
| Doorway | What approving does there |
|---|---|
| Linear, Jira, Asana, ClickUp, monday, Notion | Merges. |
| Zendesk, Intercom, Freshdesk, Help Scout, Gorgias, Front | Merges, from an internal note. |
| Slack | Merges, from the approve and deploy button in the thread. |
| Merges, from a reply to Novix’s own message. | |
| GitHub, GitLab, Bitbucket, Trello, Discord | Asks you to merge the pull request yourself. |
That last row is a deliberate line, not a gap. On those providers a commenter’s address is an opt-in profile field, admin only, or missing from the API entirely, and none of that is proof for an action that ships code. They reply with the pull request instead, and merging it uses your own repository access, which Novix records as the approval anyway.
From the dashboard
Open the task and use approve and deploy. It takes two clicks and needs the approve fixes permission, because your main branch deploys itself and merging is therefore shipping.
Novix never merges itself
No auto-summon in Novix merges a pull request. The strongest thing the agent does on its own is open one that is ready for review. Every approval, from every doorway, goes through one writer, so a fix is approved once and billed once however many places notice the merge.