Feature/add calver release process #69
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
…unneeded tomli install in other scripts
Will most likely be recondensed at a later point, but keeping the whole script pattern consistent for easier refactoring later
…te-demo not creating branches and some env var issues
…o that it remains isolated from CI interactions
…responding script prior to review
… portions to get things moving possibly
…to multiple checkout oddities arising
…e session along with fixing arg passthrough
…fault for cache folder for the time until it gets moved to config passthrough later
…r case not used commonly
…due to requirement when used in automation
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.
Adds a calender version based release process for the template itself, along with corresponding CICD to try and match up somewhat with the generated projects release process.
The two processes may diverge later on, but for the time being gitflow w/ release branches is still being used by the template to keep the two systems similar. It may make sense to move toward trunk based development directly for the cookiecutter depending on things go, but for the time being the plan is just to judge it as we go and see if it is worth deviating or not.