Skip to content

docs: describe the smoke push trigger and the full release-owned file list - #413

Merged
TMHSDigital merged 1 commit into
mainfrom
docs/smoke-push-trigger
Oct 4, 2026
Merged

TMHSDigital merged 1 commit into
mainfrom
docs/smoke-push-trigger

Conversation

@TMHSDigital

Copy link
Copy Markdown
Owner

Closes #393. Also fixes item 2 of #368 (the showcase/README.md path-filter claim).

What was stale

Claim Where Reality
"there is no push trigger" on Blender Smoke AGENTS.md (×2), CONTRIBUTING.md, PR template push: branches: [main] with paths-ignore, added in 10fcd33. The release gate waits on it for direct pushes
"blender-smoke.yml has no path filter" showcase/README.md paths-ignore: **.md, docs/**, assets/**
release force-updates v0 and v0.1 AGENTS.md v<major> and v<major>.<minor> (release.yml:235-236); v0.1 is frozen at 0.1.3
drift-check@v1.15 AGENTS.md SHA-pinned (comment: v1.19.2)
release "for content-changing paths only" AGENTS.md, CLAUDE.md § Release Hygiene No path filter. It releases on feat:/fix:/breaking subjects, gated by release-gate.sh
release-owned version field is only in .cursor-plugin/plugin.json AGENTS.md, PR template release.yml:182,212 also rewrites .claude-plugin/plugin.json and marketplace.json
label-sync "self-heals via gh label create --force" AGENTS.md Updated to match #409, which drops --force and skips forks

Evidence (inspection only; documentation change)

  • Each corrected statement was checked against the current workflow files: blender-smoke.yml:30-50, release.yml:228-240 and :182,212, drift-check.yml:18, and .github/scripts/release-gate.sh:1-14.
  • grep -rn "no .push. trigger" AGENTS.md CONTRIBUTING.md .github/ CLAUDE.md now returns nothing.
  • CLAUDE.md had no foreign working-copy hunk before this edit (git diff --quiet CLAUDE.md).

🤖 Generated with Claude Code

… list

10fcd33 added a push-to-main trigger to blender-smoke.yml so direct
pushes are smoke-tested before release, but AGENTS.md, CONTRIBUTING.md,
the PR template and showcase/README.md still said there was no push
trigger (or no path filter at all). Agents and contributors use these as
merge-evidence policy.

Also correct, from the workflows as they are now: release.yml runs on
every push and gates on commit type plus release-gate.sh (no path
filter); floating tags are v<major> and v<major>.<minor>, not v0.1;
drift-check is SHA-pinned; label-sync no longer force-recreates labels;
and the release-owned version fields include both .claude-plugin files,
not only .cursor-plugin/plugin.json.

Closes #393

Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added showcase Budget-conformance props under showcase/ documentation Improvements or additions to documentation ci labels Oct 4, 2026
@TMHSDigital
TMHSDigital merged commit bdaeb95 into main Oct 4, 2026
10 checks passed
@TMHSDigital
TMHSDigital deleted the docs/smoke-push-trigger branch October 4, 2026 23:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci documentation Improvements or additions to documentation showcase Budget-conformance props under showcase/

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: AGENTS.md, CONTRIBUTING and the PR template still say Blender Smoke has no push trigger; release-owned file lists are incomplete

1 participant