feat: CI check annotated tags in PR range - #11
Merged
Merged
Conversation
- scan tags targeting PR commits - tagger email in [identities] - tag message ASCII + no forbidden tokens - backstop for --no-verify bypass
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
1 participant
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.
Adds a CI step to
commit-lint.ymlthat scans annotated tags whose target commit is in the PR range, enforcing:[identities][forbidden_tokens]Why
git push --no-verifybypasses the localpre-push validate_tagcheck. This step is the CI backstop for that gap on annotated tags pushed within a PR.Lightweight tags are skipped here -- they have no tagger field and no message; their pointed-to commit identity is already covered by the existing commit scan step.
Scope
if: github.event_name == pull_requestguard applies).*objectname(target commit) falls inBASE..HEADare checked; pre-existing tags outside the PR range are ignored.if: success() || failure()so it runs even if the commit scan step failed -- both failures are reported in one run.