CI/CD Checks

The Checks tab in your Task Workspace shows the status of CI/CD pipelines running on your task's branch. It pulls data directly from the GitHub Checks API, giving you real-time visibility into whether the agent's code passes your quality gates.

Prerequisites

Common integrations that create check runs:

• GitHub Actions — Workflows defined in .github/workflows/*.yml (e.g., build, test, lint)
• Vercel — Automatically creates check runs when connected (build status, preview deployment status)
• CircleCI, Travis CI, CodeCov — Any GitHub App that registers check runs on commits

How It Works

1. The agent creates a branch and pushes code to your repository.
2. GitHub triggers any configured CI/CD workflows on that branch.
3. The Checks tab fetches the check runs for the latest commit on that branch using the GitHub Checks API.
4. You see the status of each check in real-time — it auto-refreshes while the task is active.

No setup is needed on the OutcomeDev side. We read whatever GitHub already provides for your branch.

What You See

Column	Description
Check Name	The specific pipeline running (e.g., "Build", "Test Suite", "Vercel")
Status	Whether it's queued, in_progress, or completed
Conclusion	The final result: success ✅, failure ❌, neutral, cancelled, etc.
Link	Click to view the full check details on GitHub

Why Your Project Might Not Show Any Checks

Scenario	Result
Repo has GitHub Actions workflows	✅ Checks appear after the agent pushes code
Repo is connected to Vercel	✅ Vercel build checks appear
Repo has no CI/CD at all	❌ "No checks running" — nothing to show
Task hasn't created a branch yet	❌ No branch means no commits to check
Branch exists but no commits pushed yet	⏳ Checks will appear once code is pushed

Setting Up CI/CD (Quick Start)

If you want checks to appear, here's the simplest way to add GitHub Actions to your repo:

1. Create a file at .github/workflows/ci.yml in your repository
2. Add a basic workflow:

name: CI
on: [push, pull_request]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm install
      - run: npm run build
      - run: npm test

3. Once this file is in your repo's main branch, every branch push (including from OutcomeDev agents) will trigger these checks automatically.

Why Checks Matter

• Proof of Correctness — A green checkmark means the code passed your defined quality gates.
• Autonomous Safety — You can trust agents to work on your repo at 3 AM knowing CI will catch regressions.
• Zero Manual Overhead — No need to manually test every change. The Checks tab tells you exactly what passed and failed.