CI: skip the build on branches that only change docs #286

Merged
jcoffey-dev merged 1 commits from ci/skip-build-docs-only into main 2026-11-03 01:19:46 +00:00
Owner

A README change shouldn't need a full Rust build. Branches that only touch top-level Markdown or docs/ now skip it. fork-checks still runs, and the run still reports success so Gitea's wait job finishes.

main keeps its full build: a push there cancels the run before it, so skipping could leave the previous merge unchecked.

This PR changes the workflow, so it builds as usual. The skip itself can only be seen on GitHub with the first docs-only branch after it lands.

A README change shouldn't need a full Rust build. Branches that only touch top-level Markdown or `docs/` now skip it. `fork-checks` still runs, and the run still reports success so Gitea's wait job finishes. `main` keeps its full build: a push there cancels the run before it, so skipping could leave the previous merge unchecked. This PR changes the workflow, so it builds as usual. The skip itself can only be seen on GitHub with the first docs-only branch after it lands.
jcoffey-dev added 1 commit 2026-11-03 01:09:18 +00:00
CI: skip the build on branches that only change docs
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 10m26s
76d90360a7
A README change took a full Rust build. A new changes job compares the branch with where it left main, and the build is skipped when only top-level Markdown or docs/ changed. fork-checks still runs, and the report still posts success, so Gitea's github job doesn't sit waiting.

Markdown elsewhere doesn't count, because vendor crates compile their READMEs in. main always builds: a push there cancels the run before it, so a docs merge that skipped its build could leave the previous merge unchecked.
jcoffey-dev merged commit 1712d1098a into main 2026-11-03 01:19:46 +00:00
jcoffey-dev deleted branch ci/skip-build-docs-only 2026-11-03 01:19:46 +00:00
Sign in to join this conversation.