Skip to main content
Blame turns AI code reviews into automated CI/CD Quality Gates. By posting native GitHub Check Runs directly to your commits, Blame can prevent unstable, untested, or vulnerable pull requests from being merged into protected branches (e.g., main or production).
Group 4 2

​
How Status Checks Work

When a pull request is opened or updated, Blame creates an in_progress GitHub Check Run. Once analysis finishes, Blame evaluates the results against your team’s quality criteria and updates the check run conclusion to success or failure.

​
Configuring Status Checks in Blame

Status check behavior can be configured per repository or organization-wide in Settings > Code Review.

​
1. Enable Status Checks (use_status_checks)

  • Enabled (Default): Automatically creates and manages GitHub Check Runs for every review run.
  • Disabled: Reviews are posted purely as conversational PR comments without creating check runs.

​
2. Required Confidence Threshold (required_confidence)

Set the baseline confidence score (from 1/5 to 5/5) required for the status check to pass:

​
3. Post Status Comments (post_status_comments)

  • Enabled (Default): In addition to the check run, posts the executive review summary comment directly to the PR conversation thread.
  • Disabled: Limits feedback to inline diff comments and check run metadata only.

​
Pass vs. Failure Criteria

A check run is marked as failure if either of the following conditions is met:
  1. Critical or High Severity Defects: Blame identified one or more critical or high severity bugs, such as broken imports, runtime exceptions, security holes, or unhandled promise crashes.
  2. Below Confidence Threshold: The calibrated confidence score falls below your configured required_confidence threshold.

​
Check Output Examples

​
Successful Check Run

​
Failed Check Run

​
Enforcing Checks in GitHub Branch Protection

To block pull requests from merging until Blame review passes:
  1. In your GitHub repository, navigate to Settings > Branches.
  2. Click Add branch protection rule (or edit your existing rule for main).
  3. Check Require status checks to pass before merging.
  4. In the search box, search for Blame or Blame CI and check the box.
  5. (Optional) Enable Require branches to be up to date before merging.
  6. Click Save changes.

​
Re-evaluating Failed Status Checks

If a pull request fails the quality gate:
  1. Apply Suggested Fixes: Reviewers or authors can click Apply suggestion on inline comments or address issues in their IDE.
  2. Push New Commits: Pushing new commits automatically triggers an incremental review run.
  3. Trigger via Slash Command: Comment /blame review or /review in the PR discussion to force an immediate re-evaluation.
  4. Check Resolution: If all critical bugs are resolved and the score meets the threshold, the check run automatically flips to success, unlocking the merge button.

​
Automated Tracking in Linear & Discord

When a check run fails with high or critical severity defects:
  • Linear: If Linear integration is connected, Blame automatically logs a tracked issue with the diff coordinates and suggested fix.
  • Slack / Discord: Alert channels receive instant notification cards with confidence metrics and direct links to the failing pull request.