Automate the release process using github actions #730
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
n3wscott
force-pushed
the
automate-releases
branch
3 times, most recently
from
ffe531f
to
bcecb54
Compare
Signed-off-by: Scott Nichols <scott@chainguard.dev>
n3wscott
force-pushed
the
automate-releases
branch
from
bcecb54
to
212a30a
Compare
|
Tested this process a lot over in https://github.com/n3wscott/releases-demo |
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.
This change in process will stop making releases in the github up for sub-modules. They are not needed at all and go mod does not look for "github releases", it looks for "git tags". So this is a change that will cause less noise in the github release section.
Signed-off-by: Scott Nichols scott@chainguard.dev