Repository navigation
Version = tag patch + merged PRs; publish only from main, dev or master - #11
Merged
Merged
Conversation
…ain, dev or master
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.
Summary
scripts/version/versionRules.{sh,ps1}, sourced bygenerateVersion): on main/master the version isMAJOR.MINOR.(newest tag patch + pull requests merged since the tag, min 1); a tagged commit is the tag; any other branch is that number plus-<commits on the branch>. Matches GitHub'sMerge pull request #Nmerge commits rather than GitLab'sinto 'main'. Today that gives0.1.4, where the previous workflow printed0.1.1-7.publish.yamlfails unless it runs onmain,devormaster: a manual run must be started on one of them (dry runs included), and a release's tag must be on one of them.GitVersion.ymlheader describe the new rule.Test plan
generateVersionboth give0.1.4for main locally