Review checks are the automated validations that run against a change while it is under review, so issues surface before a deployment ever starts rather than failing mid-pipeline. They act as a quality gate on the way into a release.
What checks run
Serpent can validate changes and run tests as part of the pipeline that moves work through review. Preflight validation runs early, so most problems are caught before the change is scoped into a release.
Acting on results
- A failing check flags the change for a fix before it can move on.
- Results stay attached to the Work Item alongside comments and approvals.
- Passing checks give reviewers confidence that the change is safe to release.