No CI pipeline: PRs merge without automated test gate

[frankbria]

Summary

The repository has no GitHub Actions CI pipeline. Pull requests (including recent ones like #450, #449, #451) merge without any automated test gate, which means:

• Regressions can ship silently
• The test suite (4200+ tests, 88% coverage) runs nowhere except locally
• There is no lint/ruff check in CI

This is a blocking concern for public launch — users/contributors submitting PRs have no automated feedback loop.

Acceptance Criteria

• GitHub Actions workflow: runs `uv run ruff check .` and `uv run pytest -m v2 -q` on every PR
• Tests must pass before merge is allowed (branch protection rule)
• Badge in README updates to reflect CI status

Suggested Workflow

```yaml

.github/workflows/ci.yml

name: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: astral-sh/setup-uv@v3
- run: uv sync
- run: uv run ruff check .
- run: uv run pytest -m v2 -q --tb=short
```

References

• `uv run pytest` — runs 4200+ tests
• `uv run pytest -m v2 -q` — runs v2 tests only (~faster)
• Coverage gate: `--cov=codeframe --cov-fail-under=85`

[coderabbitai]

🔗 Related PRs

#35 - fix: Resolve E2E test timeout failures in GitHub Actions [merged]
#189 - ci: Add npm security audit gate to deployment pipelines [merged]
#241 - feat(ui): add phase-awareness to AgentList, QualityGatesPanel, and CostDashboard [merged]
#303 - feat(gates): add BUILD validation gate for config errors [merged]
#386 - [Phase 2.5-F] Harden verification gates and add batch-level QA [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[traycerai]

Plan

Observations

• No .github/workflows/ directory exists — there is zero CI today.
• The project uses uv for dependency management (uv.lock present, pyproject.toml with [dependency-groups]).
• ruff is already a declared dependency and configured under [tool.ruff] in file:pyproject.toml.
• pytest is configured in file:pytest.ini; the v2 marker is registered there. pytest-cov is in the dev dependency group.
• file:.coveragerc sets fail_under = 60; the issue suggests 85% as a coverage gate — use the existing .coveragerc threshold (60%) to avoid breaking CI immediately, with a note to raise it.
• file:README.md already has static badge lines (lines 5–10) that need a live CI badge added.
• file:.pre-commit-config.yaml uses ruff-pre-commit at v0.2.0; the workflow should pin the same ruff version for consistency.

Approach

Create .github/workflows/ci.yml using astral-sh/setup-uv (already the project's package manager), run ruff check then pytest -m v2 with coverage, and add a live GitHub Actions badge to the README. This is the minimal, non-breaking path that satisfies all acceptance criteria.

---

Implementation Steps

1. Create .github/workflows/ci.yml

Create the directory path .github/workflows/ and add ci.yml with the following structure:

• Trigger: on: [push, pull_request] targeting all branches (or restrict to main/develop if preferred).

• Job lint:

  • runs-on: ubuntu-latest
  • actions/checkout@v4
  • astral-sh/setup-uv@v5 (latest stable; check https://github.com/astral-sh/setup-uv/releases for the current tag)
  • uv sync --frozen — installs all deps including dev group from uv.lock
  • uv run ruff check . — uses the [tool.ruff] config already in file:pyproject.toml

• Job test (depends on lint or runs in parallel — parallel is faster):

  • Same runner + checkout + uv setup steps
  • uv sync --frozen
  • uv run pytest -m v2 -q --tb=short --cov=codeframe --cov-report=xml --cov-fail-under=60
    • --cov-fail-under=60 matches the existing file:.coveragerc fail_under value to avoid immediate breakage
    • --cov-report=xml produces coverage.xml for optional upload
  • Optionally upload coverage.xml as an artifact using actions/upload-artifact@v4

Note: The issue suggests --cov-fail-under=85, but .coveragerc currently sets 60. Start at 60 to keep CI green on day one; raise the threshold in a follow-up PR once the gap is closed.

sequenceDiagram
    participant PR as Pull Request / Push
    participant GH as GitHub Actions
    participant Lint as Job: lint
    participant Test as Job: test

    PR->>GH: Trigger on push / pull_request
    GH->>Lint: checkout + uv sync + ruff check .
    GH->>Test: checkout + uv sync + pytest -m v2 --cov
    Lint-->>GH: pass / fail
    Test-->>GH: pass / fail
    GH-->>PR: Required status checks → block or allow merge

Loading

2. Add Branch Protection Rule (repository settings — not a file change)

In GitHub → Settings → Branches → Add rule for main:

• Enable "Require status checks to pass before merging"
• Add both lint and test as required checks (they appear after the first workflow run)
• Enable "Require branches to be up to date before merging"

3. Update file:README.md — Add Live CI Badge

Replace or supplement the static ![Tests] and ![Coverage] badges (lines 8–9) with a live GitHub Actions badge. Insert after line 10 (the Twitter badge):

![CI](https://github.com/frankbria/codeframe/actions/workflows/ci.yml/badge.svg)

This badge automatically reflects the current main branch CI status.

4. Pin setup-uv Version Consistently

In ci.yml, pin astral-sh/setup-uv to a specific tag (e.g., @v5) rather than @v3 (mentioned in the issue) to match the latest release. Verify the current release at https://github.com/astral-sh/setup-uv/releases before committing.

5. Verify uv sync --frozen Works in CI

The --frozen flag ensures the lockfile (uv.lock) is respected exactly, preventing silent dependency drift in CI. Confirm uv.lock is committed (it is — visible in the workspace root).

---

Summary of Files to Create / Modify

Action	File
Create	file:.github/workflows/ci.yml
Modify	file:README.md — add live CI badge

No changes to pyproject.toml, pytest.ini, or .coveragerc are needed; the existing configuration is already compatible with the workflow.

Import In IDE

🤖 Prompt for AI Agents

## Observations

- No `.github/workflows/` directory exists — there is zero CI today.
- The project uses `uv` for dependency management (`uv.lock` present, `pyproject.toml` with `[dependency-groups]`).
- `ruff` is already a declared dependency and configured under `[tool.ruff]` in `file:pyproject.toml`.
- `pytest` is configured in `file:pytest.ini`; the `v2` marker is registered there. `pytest-cov` is in the `dev` dependency group.
- `file:.coveragerc` sets `fail_under = 60`; the issue suggests 85% as a coverage gate — use the existing `.coveragerc` threshold (60%) to avoid breaking CI immediately, with a note to raise it.
- `file:README.md` already has static badge lines (lines 5–10) that need a live CI badge added.
- `file:.pre-commit-config.yaml` uses `ruff-pre-commit` at `v0.2.0`; the workflow should pin the same ruff version for consistency.

## Approach

Create `.github/workflows/ci.yml` using `astral-sh/setup-uv` (already the project's package manager), run `ruff check` then `pytest -m v2` with coverage, and add a live GitHub Actions badge to the README. This is the minimal, non-breaking path that satisfies all acceptance criteria.

---

## Implementation Steps

### 1. Create `.github/workflows/ci.yml`

Create the directory path `.github/workflows/` and add `ci.yml` with the following structure:

- **Trigger:** `on: [push, pull_request]` targeting all branches (or restrict to `main`/`develop` if preferred).
- **Job `lint`:**
  - `runs-on: ubuntu-latest`
  - `actions/checkout@v4`
  - `astral-sh/setup-uv@v5` (latest stable; check [https://github.com/astral-sh/setup-uv/releases](https://github.com/astral-sh/setup-uv/releases) for the current tag)
  - `uv sync --frozen` — installs all deps including dev group from `uv.lock`
  - `uv run ruff check .` — uses the `[tool.ruff]` config already in `file:pyproject.toml`

- **Job `test`** (depends on `lint` or runs in parallel — parallel is faster):
  - Same runner + checkout + uv setup steps
  - `uv sync --frozen`
  - `uv run pytest -m v2 -q --tb=short --cov=codeframe --cov-report=xml --cov-fail-under=60`
    - `--cov-fail-under=60` matches the existing `file:.coveragerc` `fail_under` value to avoid immediate breakage
    - `--cov-report=xml` produces `coverage.xml` for optional upload
  - Optionally upload `coverage.xml` as an artifact using `actions/upload-artifact@v4`

> **Note:** The issue suggests `--cov-fail-under=85`, but `.coveragerc` currently sets 60. Start at 60 to keep CI green on day one; raise the threshold in a follow-up PR once the gap is closed.

```mermaid
sequenceDiagram
    participant PR as Pull Request / Push
    participant GH as GitHub Actions
    participant Lint as Job: lint
    participant Test as Job: test

    PR->>GH: Trigger on push / pull_request
    GH->>Lint: checkout + uv sync + ruff check .
    GH->>Test: checkout + uv sync + pytest -m v2 --cov
    Lint-->>GH: pass / fail
    Test-->>GH: pass / fail
    GH-->>PR: Required status checks → block or allow merge
```

### 2. Add Branch Protection Rule (repository settings — not a file change)

In **GitHub → Settings → Branches → Add rule** for `main`:
- Enable **"Require status checks to pass before merging"**
- Add both `lint` and `test` as required checks (they appear after the first workflow run)
- Enable **"Require branches to be up to date before merging"**

### 3. Update `file:README.md` — Add Live CI Badge

Replace or supplement the static `![Tests]` and `![Coverage]` badges (lines 8–9) with a live GitHub Actions badge. Insert after line 10 (the Twitter badge):

```
![CI](https://github.com/frankbria/codeframe/actions/workflows/ci.yml/badge.svg)
```

This badge automatically reflects the current `main` branch CI status.

### 4. Pin `setup-uv` Version Consistently

In `ci.yml`, pin `astral-sh/setup-uv` to a specific tag (e.g., `@v5`) rather than `@v3` (mentioned in the issue) to match the latest release. Verify the current release at [https://github.com/astral-sh/setup-uv/releases](https://github.com/astral-sh/setup-uv/releases) before committing.

### 5. Verify `uv sync --frozen` Works in CI

The `--frozen` flag ensures the lockfile (`uv.lock`) is respected exactly, preventing silent dependency drift in CI. Confirm `uv.lock` is committed (it is — visible in the workspace root).

---

## Summary of Files to Create / Modify

| Action | File |
|--------|------|
| **Create** | `file:.github/workflows/ci.yml` |
| **Modify** | `file:README.md` — add live CI badge |

No changes to `pyproject.toml`, `pytest.ini`, or `.coveragerc` are needed; the existing configuration is already compatible with the workflow.

---

Execution Information

Branch: main
Commit: 4308b0a

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.