Repository navigation
ci(auto-tag): stamp-marker trap lore + T43ci incident (#710 follow-up; merging re-arms develop stamping) - #713
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #713 +/- ##
===========================================
+ Coverage 76.10% 85.55% +9.44%
===========================================
Files 109 109
Lines 5319 13689 +8370
Branches 608 1471 +863
===========================================
+ Hits 4048 11711 +7663
- Misses 1084 1848 +764
+ Partials 187 130 -57
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…ollow-up) The skip-ci matcher is a substring scan of the WHOLE commit message, so any commit quoting the bracketed marker skips itself. Proven twice on 2026-10-08: #710's head commit (marker quoted in its subject) skipped its own checks, and #710's merge commit (original PR title embedded in the merge body) skipped the auto-tag stamp push outright -- develop sat unstamped at d03530a. No behavior change: the merged guard already checks bot author identity + full devN-shaped subject (GH-Copilot #710 review). This adds the header LORE next to the guard so the next editor cannot re-introduce the literal, and rewrites T43ci with the incident and its still-open closing observations. Merging this PR (clean title/body, no bracketed literal anywhere) is also the recovery: its merge push re-triggers auto-tag, which stamps develop again.
JavierGOrdonnez
force-pushed
the
jgo/autotag-followups
branch
from
October 8, 2026 14:27
a24084c to
9d24a12
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #710 (which merged with Copilot's stricter guard — author email + devN-shaped subject — already in place)
Zero behavior change. Two documentation deltas:
d03530acsince 14:16.X.Y.Z.devNsubject shape; check-pr rejects human-introduced.devN— inherited-unchanged stamps pass,auto_version.py:343— so humans cannot mint the subject+author pair the guard matches) and refreshed closing observations. (v2: narrowed per Copilot review r4220171346/r4220171484.)Merging this PR is also the recovery: its merge commit carries no bracketed literal anywhere (title/body checked), so the push to develop re-triggers auto-tag with the new code → develop gets stamped (
1.6.4.dev2prerelease) and the first-ever skip-ci-free stamp push demonstrates the visibility fix.Note for reviewers: please do NOT add the bracketed marker to this PR's title/body on edit — it re-skips the very stamp push we are waiting for.