GuidesCI/CD Integration

CI/CD Integration

Enforce AIM governance automatically on every pull request.

GitHub Action

Add the Manifest AIM GitHub Action to your workflow:

# .github/workflows/aim-enforce.yml
name: AIM Governance
 
on:
  pull_request:
    branches: [main, develop]
  push:
    branches: [main]
 
permissions:
  contents: read
  pull-requests: write
 
jobs:
  enforce:
    name: Enforce AIM Governance
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
 
      - name: Enforce AIM manifest
        uses: RCOLKITT/Manifest-AIM/manifest-aim/action@main
        with:
          manifest: aim.yaml
          target: src/
          environment: production
          fail-on-warnings: false
          report: true

Action Inputs

InputDefaultDescription
manifestaim.yamlPath to AIM manifest
target.File or directory to enforce
environment—Environment override
fail-on-warningsfalseExit 1 on warnings
reporttrueGenerate JSON report artifact

Action Outputs

OutputDescription
violationsTotal violation count
blockedWhether blocking violations exist
report-pathPath to JSON governance report

JSON Governance Report

Use --report for machine-readable output:

manifest enforce src/ --report
{
  "manifest": "aim.yaml",
  "summary": {
    "files": 42,
    "totalViolations": 3,
    "blocked": true,
    "byAction": { "block": 2, "warn": 1 },
    "bySeverity": { "critical": 2, "warning": 1 }
  },
  "results": [...]
}

Environment-Specific Enforcement

Use when conditions to apply different rules per environment:

governance:
  rules:
    - name: no-console-production
      when: "environment == 'production'"
      detect:
        type: pattern
        match: "console\\.(log|debug)\\("
      action: block
      severity: error

Then in CI:

manifest enforce src/ -e production
Composing ManifestsCLI Commands