create GitHub action #91
Merged
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
pass path to config file: this was annoying to figure out. there's no manpage or other docs for this I found the option at goreleaser/goreleaser#2644 It's also annoying that I need this file at all; I feel that I should be able to pass the options to goreleaser directly, but don't know how to.
apparently when I use this matrix, it sets this directory differently... also fix windows binary names
|
I feel you with not being impressed by GitHub Actions. I've had similar issues trying to get it to do what I want over in anacrolix/torrent. I think CircleCI is still doing unit tests and stuff, so until those are here in actions too, it might be appropriate to leave those running. |
|
I merged into a new branch |
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 action will provide artifacts in the actions tab on GitHub after every push or pull request1. When a semver tag is pushed2, it'll also create a release for it and upload the artifacts to the release. You can see what the release looks like by looking at my fork (
git tag v99.99.99; git push origin v99.99.99gives you this) I'm sure there's a cleaner way to do this, but frankly I've spent hours on this already 3, and want to go do something else now.If you want to, you can probably remove the circle ci option now.
Footnotes
you can easily remove the pull request option. I left this in because sometimes people (quite often me) don't want too set up a dev environment to fix small issues. ↩
it doesn't like tags that aren't semver. It falls. No artifacts are uploaded. ↩
I've been lazy about learning GitHub actions until now ↩