Codeac pull request status check merge blocking behavior

Question

Codeac integrates with repository hosting services to post automated review statuses and comments on pull requests.

The goal is to configure Codeac so that a failed static-analysis status prevents merging a pull request protected by required status checks. It is unclear whether Codeac writes a commit status that the repository host can enforce as a required check, or whether it only publishes advisory review comments without affecting merge eligibility. The required permission boundary also depends on the installed Codeac application scope rather than Codeac alone.

Does Codeac expose a status check that branch protection can require? What repository app permissions must the Codeac installation hold to block merges? Is there a configuration option to enforce Codeac review status as a merge gate?

Tasadduq Burney · Answer

Direct answer: Codeac can create a commit status that repository hosts treat as a required check, allowing branch protection to block merges when that status fails, provided the app has the proper permissions and the host’s protection rule is configured to require the status.
Likely explanation: Codeac’s integration posts a status (often named "Codeac") on the commit linked to the pull request. If the repository’s branch protection is set to "require status checks before merging" and the "Codeac" status is selected, a failed static‑analysis status will prevent the merge.
Confirmed facts: The Codeac repository app must have at least the statuses write scope and pull_requests read scope to post a commit status. The host (GitHub, GitLab, Bitbucket, etc.) must support required status checks, and the rule must be enabled. No universal "required status" flag exists in Codeac itself; the enforcement relies on the host’s protection settings.
Steps to verify for your case:

Install the Codeac app in the target repository and open the app’s settings.
  Confirm the granted permissions include statuses (write) and pull_requests (read).
  Open a pull request and check the commit status list; a status named "Codeac" should appear after the analysis runs.
  In the repository’s branch protection rules, ensure "require status checks before merging" is enabled and that the "Codeac" status is listed as a required check.

Missing diagnostic detail: Which repository platform are you using (e.g., GitHub, GitLab, Bitbucket)? The exact support for required status checks and the way branch protection selects statuses can vary.

Codeac pull request status check merge blocking behavior

1 answer

Your perspective belongs here.

1 question comment

Status Check Payload Detail