Skip to content

fix(ci): make the lint gate read-only - #88

Merged
hseshadr merged 2 commits into
mainfrom
fix/read-only-lint-gate
Oct 24, 2026
Merged

hseshadr merged 2 commits into
mainfrom
fix/read-only-lint-gate

Conversation

@hseshadr

Copy link
Copy Markdown
Collaborator

What

poe lint ran ruff check --fix and ruff format in place, so dagger call ci could rewrite a dirty tree and still exit 0. It now runs ruff check and ruff format --check, matching the three module gates (portfolio-foundation, cloudflare-pages, python-package).

A formatting or auto-fixable lint regression now fails the hosted gate instead of being silently repaired inside the container.

Tests

  • uv run poe lint: clean on this tree.

Note

gate still runs lint first, so a developer who wants the old convenience can run uv run poe lint --fix locally; the hosted gate is the one that must be read-only.

`poe lint` ran `ruff check --fix` and `ruff format` in place, so the hosted
gate could rewrite a dirty tree and still exit 0. It now runs `ruff check` and
`ruff format --check`, matching the three module gates: a formatting regression
fails instead of being silently repaired inside the container.

Tests: uv run poe lint.
The control plane reads cross-repo state and writes packages but had no
SECURITY.md. Document the private channel and the in-scope bypasses: source
guard, secret scan, fleet evidence, and workflow injection.
@hseshadr
hseshadr merged commit c42e543 into main Oct 24, 2026
3 checks passed
@hseshadr
hseshadr deleted the fix/read-only-lint-gate branch October 24, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant