CI Pipeline must pass
The merge request pipeline must complete successfully before the task can be closed. No more merging code that hasn't been validated by your CI system.
Feature
Tasks are done when the gates say so
Quality Gates let teams define the exact conditions that must pass before a task is considered complete — from a green pipeline to coverage thresholds — enforced automatically, every time.
Built-in gates
Every standard your team already cares about
Orchestrator ships with the gates most teams need out of the box. Enable the ones that apply to your project and configure them to your standards.
No merge conflicts
The branch must be free of conflicts with the target branch. Orchestrator blocks completion until the merge request is rebased and conflicts are resolved.
Minimum code coverage
Enforce a project-specific coverage threshold. Tasks are blocked from completion if the MR drops coverage below the configured minimum — keeping technical debt in check.
Required approvals
Specify how many peer reviews the merge request must receive before the task is marked done. Enforce your team's code review standards automatically.
Security scan clear
Block completion if the security scan reports new critical or high-severity vulnerabilities. Ship with confidence that every merge has been checked.
Custom gates
Define your own gates using project-specific rules. Check for documentation updates, migration files, changelog entries, or any other condition your workflow requires.
How it works
Automated enforcement, zero overhead
Quality Gates run in the background. Your developers focus on the work — Orchestrator ensures nothing slips through the cracks.
Configure gates per project
Choose which quality gates apply to each project. Set thresholds, required approvals, and custom conditions — all stored in your project configuration.
Work as usual
Developers work normally. Orchestrator monitors the merge request status in the background, tracking each gate's current state as the pipeline runs.
Gates are checked automatically
When a task is ready to close, Orchestrator evaluates every configured gate. Failing gates block completion with a clear explanation of what needs to be resolved.
All green — task is done
Once every gate passes, the task is marked complete and the merge request can proceed. No manual checklist, no forgotten steps.
Configuration
Your standards, your rules
Quality Gates are fully project-specific. Each team sets the bar that makes sense for their codebase and release process.
Project-level configuration
Each project defines its own set of quality gates and thresholds. A library project might require 90% coverage; a prototype might only require a passing pipeline.
Adjustable thresholds
Coverage minimums, required approval counts, and severity levels are all tunable. Set the bar your project needs, not a one-size-fits-all default.
Authorized overrides
Project owners and admins can bypass a gate with an explicit justification. Emergencies happen — Quality Gates give you an escape hatch without removing accountability.
Live gate status
Every task shows the real-time status of its gates. Developers know exactly which gates are pending, passing, or failing — without leaving the Orchestrator interface.
Stop merging code that isn't ready
Join the early access program and let Orchestrator's Quality Gates enforce your team's merge standards automatically — every task, every time.