46b3d88ae5
## What is this? Just adding documentation for using cosign with GitHub's OIDC in CI. ## Why? I spent 4 hours looking through goreleaser and GitHub's docs before I finally discovered I was missing the `id-token: write` permission in my workflow file. This PR serves to just include the `id-token: write` scope in the `CI -> (GH) actions` section of the docs to hopefully save other devs the trouble 🤣 ### Additional I also considered adding this to docs for the other CI providers, but I am not too familiar on the OIDC side of things; might be worth considering for the team? Cheers --- Been using goreleaser for one of my [oss projects](https://github.com/caffeine-addictt/waku) recently and it's been great! Just wanted to contribute something back, keep up the great work! :> Signed-off-by: AlexNg <contact@ngjx.org>
GoReleaser
Deliver Go binaries as fast and easily as possible.
GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.
Get GoReleaser
Documentation
Documentation is hosted live at https://goreleaser.com
Community
You have questions, need support and or just want to talk about GoReleaser?
Here are ways to get in touch with the GoReleaser community:
You can find the links above and all others here.
Code of Conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. We appreciate your contribution. Please refer to our contributing guidelines for further information.
Badges
GitHub Sponsors
High-tier sponsors of @caarlos0 on GitHub:
OpenCollective
Sponsors
Does your company use goreleaser? Help keep the project bug-free and feature rich by sponsoring the project.
Backers
Love our work and community? Become a backer.
Contributors
This project exists thanks to all the people who contribute. [Contribute].
Stargazers over time
