Skip to content

CI Gate Requirements

This section documents the CI gate configuration for all repositories consuming standard-actions. It covers which checks are required and the security scanning requirements.

Overview

Every managed repository runs a common set of CI checks on pull requests. CI workflows trigger on pull_request only — push triggers are not used because branch protection enforces that all changes go through PRs. These checks are organized by category using job name prefixes:

Prefix Purpose Example jobs
ci: Code quality and standards validation ci: standards-compliance, ci: actionlint
security: SAST and vulnerability scanning security: codeql, security: semgrep
test: Unit and integration tests test: unit, test: integration
release: Release gate validations release: gates

Key concepts

  • Required status checks — Configured in GitHub repository rulesets. PRs cannot merge until all required checks pass.
  • Self-referencing CI — The standard-actions repository tests its own actions using local paths (./actions/...).

Pages in this section