Skip to main content
Approval gates and policies

AI approval gates for pull requests

Volath adds AI approval gates for pull requests. Policies hold steps back until a human approves them, so you decide where the pipeline stops.

Benefits

What you get

  • Keep a human decision where it matters.
  • Limit auto-run by label and by AI spend per ticket.

How it works

How it works

It runs on your own machine. Your code, tickets and settings live in a local SQLite database, or in your own MySQL or MariaDB.

  1. By default the pipeline runs on by itself, and nothing is held until a policy is turned on.

  2. In Project settings › Policies, require approval before the AI starts developing, before the pull request is opened, or before the merge into staging.

  3. Or auto-run only tickets with a label such as safe, and only while the AI spend on the ticket stays under a limit.

  4. A held ticket shows in Needs attention and in its drawer, where it can be approved or rejected.

  5. The chat assistant can do it on request, and so can POST /api/tickets/{id}/approve and /reject.

  6. An approval.requested webhook event is sent when a step is held.

  7. A workflow can also hold a ticket with a Gate step or a request-approval action.

Take your next ticket from idea to merged code

It runs on your own machine. Your code, tickets and settings live in a local SQLite database, or in your own MySQL or MariaDB.

Back to all Volath features · Extend Volath with plugins