auto-release: skip releases for docs-only merges [skip release]#11
Merged
Conversation
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.
Docs-only merges now skip the auto-release even without a
[skip release]marker: if every file the merge changed is documentation (*.md,docs/, or an image asset.gif/.png/.jpg/.jpeg/.webp/.svg), there is no app change to version, so no patch release is cut.Belt-and-suspenders follow-up to the v0.1.6 incident (a docs-only GIF merge cut a release because a PR-title
[skip release]did not reach the squash subject). The squash subject is nowPR_TITLE, which makes the marker reliable; this makes the common case (README / screenshot / GIF merges) safe even if the marker is forgotten.Notes:
[skip release]subject check; non-doc or mixed changes release exactly as before.wc -lvsgrep -Ec), notgrep -qv, becausegrep -qvexit codes differ between BSD and GNU grep — tested both paths locally.[skip release]in this PR title so adding the guard does not itself cut a release.