Pull request checks and status

Checks provide automated evidence

Pull requests can display checks from GitHub Actions and other integrations. Checks may compile the project, run tests, lint code, scan dependencies or verify deployment requirements.

Passing checks are not the entire review

Automation catches repeatable problems, but reviewers still need to inspect design and behavior. A green build means the configured checks passed; it does not prove that every requirement is correct.

Required checks

Repositories can require selected checks before a protected branch accepts a pull request. This makes quality gates consistent instead of relying on memory.