Skip to content

ci: skip CI on draft PRs; marking a PR ready starts it - #185

Merged
fts-forge[bot] merged 1 commit into
mainfrom
ci/skip-drafts
Nov 18, 2026
Merged

fts-forge[bot] merged 1 commit into
mainfrom
ci/skip-drafts

Conversation

@fts-forge

@fts-forge fts-forge Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Summary

CI no longer runs on draft PRs: it starts when the PR is marked ready for review, and runs on every push after that.

  • ci.yml: check (hosted, devenv, clippy/tests/wasm, ~60 min ceiling) is skipped on a draft. No required checks on main.
  • Gate: if: github.event_name != 'pull_request' || github.event.pull_request.draft == false, combined with && and parentheses where a job already had an if:. It is a job-level skip, not a trigger filter, so a skipped job still reports.
  • The pull_request trigger lists opened, synchronize, reopened, ready_for_review. Concurrency is unchanged: per-PR group, a newer push cancels the older run, and marking ready replaces the all-skipped draft run.
  • The agent doc now says that CI runs on ready PRs only and that you mark the PR ready to get checks.

How tested

actionlint on the changed workflows. This PR is not a draft, so its own CI runs.

🤖 Generated with Claude Code

Every job that runs on a pull request is skipped while the PR is a draft
(job-level if:, so a skipped job still reports). The pull_request trigger
lists ready_for_review, so marking a PR ready starts the run; every push
after that runs it again and cancels the older run. Pushes, dispatches and
tags are unchanged. The agent doc says to mark a PR ready to get checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fts-forge
fts-forge Bot merged commit e0eb25e into main Nov 18, 2026
1 check passed
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.

0 participants