Skip to content

docs: warn that describing the skip-ci token in a commit message suppresses CI #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mcarter-astronautdev merged 1 commit into from
Aug 2, 2026
Merged

docs: warn that describing the skip-ci token in a commit message suppresses CI #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/fleet-operations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,14 @@ byte-identical everywhere does not.
`[skip ci]` suppresses workflow triggers but **not** GitHub's own "Dependabot Updates" scheduler —
seeing one of those fire after a wave is expected and benign.

> **Never write the literal token in a commit message that is not itself a wave.** GitHub scans the
> **whole** commit message, not just the subject line, so a commit that merely *describes* the
> technique suppresses its own CI. This bit the commit that first added this document: it explained
> the wave pattern in its body, and the resulting PR came back with **zero check runs** — not failed,
> not queued, simply absent, which reads exactly like a healthy PR whose checks have not started yet.
> Write it as `skip-ci` in prose, and if a PR ever reports no checks at all, grep the commit message
> before looking anywhere else.

### Execution shape

One atomic commit per branch via the Git Data API (blobs → tree → commit → ref patch), not one
Expand Down