feat: calendar versioning workflow + labels update#43
Closed
Conversation
Author
|
Closing in favor of another PR |
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.
Motivation + Changes
semverrelated workflows since the main repositories which use these (Core, Pro, Templates and Snowflake) are moving away from semantic versioning and using calendar versioning instead.calver: monthly,calver:patchandcalver: breaking.pr-enforce-semver-labels.yml->pr-enforce-calver-labels.yml(since no repos directly used the semver version of this workflow, it is safe to update)pr-enforce-no-major-minor.yml ->pr-enforce-patch-only.yml(updated to support calver too and updated naming to make sense for both)pr-enforce-labels->pr-enforce-label-groups(renamed to make it clearer since it's enforcing all the labels, such as notes, docs and calver in this case. all the places that use this will use calver so there's no conflict here)+pr-enforce-notes-labels(i noticed thatpr-enforce-semver-labels.ymlisn't used anywhere, andpr-enforce-docs-labels.ymlis only used in one repo. keeping the separate ones are good as it means you can use the label requirements meant for your repo, so i've added the notes labels workflow for completion and used all three inpr-enforce-label-groupswhich allows all repos which use it to keep to the same format, or use the existing ones individually)Additional Changes