Update example automated tagging workflow to include master branch #7
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
|
🏷️ [bumpr] |
JohnBrittaein
approved these changes
Jul 3, 2025
|
🚀 [bumpr] Bumped! |
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.
Description
Currently, the workflow for automatically tagging versions only accounts for a default branch named
main, but many repositories under the organization still have the legacy default,master. While we should strive to update all of the default branch names tomain, that is a longer endeavor. In the meantime,RxnRover/.github/.github/workflows/tag_version_and_release.ymlserves as an example file when we apply the workflow to our repositories. Since it may be applied to repositories with either default branch name, I think it makes sense to update this file to avoid forgetting to update it when we copy over to certain repositories.