workspace-enforce

A CI health gate blocks merges when unwaived high-severity audit violations are detected. It runs in pre-commit and pre-merge contexts to enforce repository quality standards before code reaches main.

Yes, you can suppress known audit findings without removing the CI merge gate by using a JSON waiver file. This temporarily suppresses specific high-severity violations while fixes are being implemented.

A pre-commit workspace health gate automates repository quality checks by blocking merges when high-severity violations are active. It exposes clear exit codes and JSON telemetry for automation and waiver policy integration.

Yes, the workspace health gate works with existing CI automation pipelines by exposing clear exit codes and JSON telemetry. This allows automation tools to parse gate results and conditionally block or allow merges.

The best way to automate merge blocking is running a workspace health gate in CI workflows. It blocks merges when unwaived high-severity violations are detected and integrates with a JSON waiver policy for exceptions.

You should use a waiver file instead of ignoring audit findings because it temporarily suppresses specific high-severity violations while keeping the merge gate active. This ensures unwaived violations still block PRs and prevents messy code from entering main.