-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature(ci): release gemini using goreleaser and github actions #427
Conversation
d5d19f5
to
09c4bc8
Compare
09c4bc8
to
ff79840
Compare
Signed-off-by: Dusan Malusev <[email protected]>
ff79840
to
1800cc8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
name: goreleaser | ||
|
||
on: | ||
push: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When do you want it to be triggered ? Currently it is going to be run on every push
for every branch.
We can trigger it when:
- Maintainer calls it via actions tab
on:
workflow_dispatch
- Make it triggered automagically if PR have label is being merged:
on:
pull_request:
branches:
- main
types: [closed]
jobs:
my-action:
if: ${{ github.event.pull_request.merged }}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's not correct, read the next line, it's limited to tag pushes only
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we might want to limit this to the master branch.
but this workflow, won't be running on PRs
In order to make use of goreleaser, we need GitHub Action to build and
gemini
and generate changelogThis is the action to do so.
Commented out
blob
Inside the repository, we don't have any AWS Keys to upload gemini binaries to S3 Bucket. until that gets sorted out, it is better to leave it commented and have the gemini release as soon as possible to test the #424 in SCT.