weekly release workflow #185
Closed
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
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
mat007
reviewed
Sep 15, 2021
Contributor
mat007
left a comment
mat007
left a comment
There was a problem hiding this comment.
Is there any way we can do a release only if there has been changes since the last one?
Maybe comparing the hash of the master branch head to the hash of the last release, or something like that?
Collaborator
Author
|
@mat007 we could do some |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Automated weekly release workflow every Wednesday as
v1.{{week count}}.0(jenkins-style)example run on https://github.com/ndeloof/compose-go/releases/tag/v1.0.0
close #118
(I would update workflow before merge so we get an initial release)