CI/CD

Automated reviewin CI/CD pipelines

Quality gates belong next to unit tests and deploy stages. Run CodeCritic in GitHub Actions, GitLab CI, or any runner that can call HTTP or shell out to the official Action.

pipeline nativemerge gatesparallel jobsartifactsrepeatable
How it works

CI patterns that work

Teams treat review like any other required job with clear ownership and rollback.

  • Feature branches: report-only reviews so authors learn without red builds.
  • Release branches: blocking severity enabled before tag promotion.
  • Hotfix lanes: expedited jobs with narrower path filters on touched services.

Workflow

How teams wire it

  1. 1

    Model the pipeline

    Decide whether review blocks deploy, runs in parallel, or only on release tags.

  2. 2

    Cache checkout

    Reuse workspace artifacts between test and review jobs to keep wall time down.

  3. 3

    Export results

    Upload findings JSON as a CI artifact for auditors or downstream bots.

  4. 4

    Iterate thresholds

    Adjust fail-on severity after measuring false positive rate for two weeks.

Examples

Integration examples

Stage after test, before deploy

Review job depends on green tests.

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - run: npm test

  ai-review:
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: codecritic/review-action@v1
        with:
          api-key: ${{ secrets.CODECRITIC_API_KEY }}

FAQ

Common questions

Latency scales with diff size and model routing. Most teams run review parallel to integration tests to hide wall time.

Related pages

GitHub ActionREST APIPre-merge

Make review a required pipeline stage

Add one job to your default branch workflow and compare build times with review parallelized.

Integrations