Skip to content

ci: skip the stamp only on the bot's own subject line, not on any mention #36

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
mmcky merged 2 commits into from
Sep 14, 2026
Merged

ci: skip the stamp only on the bot's own subject line, not on any mention #36

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b9d8eed
ci: skip the stamp only on the bot's own subject line, not on any men…
mmcky Sep 14, 2026
f454b63
ci: scope the skip-stamp guard to push events explicitly
mmcky Sep 14, 2026
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
6 changes: 5 additions & 1 deletion .github/workflows/stamp-version.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,12 +23,16 @@ jobs:
stamp:
# The bot's own commit carries [skip-stamp]; pushes made with GITHUB_TOKEN
# don't retrigger workflows anyway, so this guard is belt-and-suspenders.
# Match the subject line only: a squash commit carries the PR body, and #35's
# body merely mentioned "[skip-stamp]" — which skipped the stamp it shipped.
# That same no-retrigger behaviour means the stamp push does not redeploy
# the site on its own — and since v0 stamping, the stamp commit is where
# `version: 0` and the README's `v0` cell first appear, so the last step
# dispatches deploy.yml explicitly (a workflow_dispatch call from
# GITHUB_TOKEN does run; only events *caused by* its pushes are dropped).
if: ${{ !contains(github.event.head_commit.message, '[skip-stamp]') }}
# A manual run (workflow_dispatch) always runs — stamp.mjs handles starting
# from the bot's own commit — so the guard applies to push events only.
if: ${{ github.event_name != 'push' || !startsWith(github.event.head_commit.message, 'Stamp QEP version hash and sync README [skip-stamp]') }}
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
Expand Down