Skip to content

P4.VER.003 — Repository has CI configuration

Field Value
Principle P4 (Verifiability)
Severity info
Evidence strong
Stability experimental

What it checks

Checks for the presence of CI configuration files or directories:

  • .github/workflows/ (GitHub Actions)
  • .gitlab-ci.yml / .gitlab-ci.yaml (GitLab CI)
  • .circleci/ (CircleCI)
  • Jenkinsfile (Jenkins)
  • .travis.yml (Travis CI)
  • azure-pipelines.yml (Azure DevOps)
  • .buildkite/ (Buildkite)
  • bitbucket-pipelines.yml (Bitbucket)
  • .woodpecker.yml (Woodpecker CI)

Only fires when the repo has source code (detected via language files).

Why it matters

A repo without CI is "locally verifiable but not continuously verified." Agents need CI to confirm their changes pass on a clean environment, not just on the developer's machine.

When to care

  • Care for any project with collaborators or agent-driven changes.
  • Care less for personal scripts or documentation-only repos. Suppress with a rationale.

How to fix

Add a CI configuration for your platform. Example for GitHub Actions:

name: ci
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: make test

History

  • 0.3.x — introduced at stability: experimental.