We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
goreleaser check
Originally posted by @rootulp in #2437 (review)
Should we add a CI workflow that runs goreleaser check to make sure that the .goreleaser.yaml is always valid?
The text was updated successfully, but these errors were encountered:
We're considering adding more distributions / architectures in #2567 so I think it makes sense to do this now.
Sorry, something went wrong.
ci: check if goreleaser config is valid (#2652)
93868b9
Closes #2452 ## Testing Tested on my fork ``` /opt/hostedtoolcache/goreleaser-action/1.21.2/x64/goreleaser check • checking path= • 1 configuration file(s) validated • thanks for using goreleaser! ``` Ref: https://github.com/rootulp/celestia-app/actions/runs/6473546638/job/17576484916?pr=39#step:3:16
af8b448
Closes celestiaorg/celestia-app#2452 ## Testing Tested on my fork ``` /opt/hostedtoolcache/goreleaser-action/1.21.2/x64/goreleaser check • checking path= • 1 configuration file(s) validated • thanks for using goreleaser! ``` Ref: https://github.com/rootulp/celestia-app/actions/runs/6473546638/job/17576484916?pr=39#step:3:16
rootulp
Successfully merging a pull request may close this issue.
Context
Originally posted by @rootulp in #2437 (review)
Proposal
Should we add a CI workflow that runs
goreleaser check
to make sure that the .goreleaser.yaml is always valid?The text was updated successfully, but these errors were encountered: