Project quality gates
Opt-in merge and release blocking rules per pillar — configure thresholds in project settings.
Quality gates are opt-in. Until you configure them under Project settings → Quality gates, VisualQ does not block PR merges, release status, or CI runs based on project policy.
Where to configure
- Open a project in VisualQ
- Go to Settings → Quality gates
- Click Add gate on each active pillar you want to enforce
- Enter explicit thresholds (required fields — no implicit defaults)
- Save
Only enabled quality modules for the project can receive gates. Disabled modules show a link to Quality modules.
What gates affect
| Surface | Behavior without gates | With configured gates |
|---|---|---|
| Project overview Release gate | Clear (no automatic blockers) | Blocked when a configured pillar exceeds its threshold |
MCP / CI gate_pr_quality | blockMerge: false (unless MCP overrides) | Evaluates configured pillars only |
| CI perf/a11y budgets | Workflow inputs only | Injects budgets from perf/a11y gate config when CI omits them |
MCP override
gate_pr_quality accepts optional inputs (includeVrt, includeFrt, includeA11y, includeHealth, threshold, a11yBudgets) that override the saved project policy for that invocation.
Without project gates and without explicit MCP includes, nothing is checked.
Global options (when ≥1 pillar gate)
- Threshold mode —
balancedorstrict(passed to blocker identification) - Coverage warning — optional PR-only warn when rolling health coverage is below your percent (does not block merge by itself)