docs: tell how to push one tag; that rc start with n=0#3222
Merged
rickeylev merged 1 commit intobazel-contrib:mainfrom Aug 29, 2025
Merged
docs: tell how to push one tag; that rc start with n=0#3222rickeylev merged 1 commit intobazel-contrib:mainfrom
rickeylev merged 1 commit intobazel-contrib:mainfrom
Conversation
dougthor42
approved these changes
Aug 28, 2025
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
2 participants
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.
If your local repo tags don't match the remote, then
git push --tagswill push alltags. This confuses the release workflow and it doesn't trigger properly. It can also
push junk tags and trigger an accidental release (hence how a 0.1 release showed up
months ago; I accidentally pushed a junk tag).
Along the way, mention that N=0 to start with for RCs