Improve release workflows by auto-detecting release date #359
Conversation
This file contains 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
rolandkakonyi
force-pushed
the
feature/improve-finish-release-workflow
branch
from
00cbd9e to
2d85db8
Compare
|
Not sure I understand where the date gets autogenerated.. The changes look the exact same as here: #305 Am I missing something? |
@zigavehovec Turns out I used wrong branch state on this one. Will open another PR with the proper changes. Sorry for the confusion! |
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
These changes reduce the manual work for performing the release by auto-detecting the release date and updating the changelog.
Changes
Changed to remove the need for entering the desired release date when starting a release.
This is now auto-detected when the release actually happens.
Checklist
CHANGELOGentry - CI change only, not applicable