ci: add sdist with vendor for release workflow #797
+37
−0
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.
OK, this is the first part for #793, the simplest one. This job will create a useful for distributions source tarball, which contains the code &
go mod vendor
run inside.Required setup in configuration:
release
(this is the name I used here, you can choose another one and I'll modify it here)Required reviewers
and add yourself in there. When you create a new tag, you'll receive an email where you need to approve the run. It helps with accidental tag push before everything is pushed :)Workflow explanation:
v
, for examplev1.51.0
.go mod vendor
.tar.gz
file containing a directory namedredis_exporter-v${version}
, under which all content is found includingvendor/
dir.I've tested this workflow on my fork, it generated this file redis_exporter-0.0.9999.tar.gz (yes, I used quite weird version)
My next step
Add another job to this workflow, which would build the binaries, and add them as assets to the same draft release.