Readme: Short section about (pre-)release process
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I just came into the situation where I wanted to have a pre-release for a branch and was not sure how to do so. I guess I could twiddle with goreleaser on my branch so it builds + releases it. A few lines on this would be awesome!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the README and investigate how GoReleaser is used for normal releases. Document the steps for creating a pre-release from a branch, including the relevant commands or configuration, so a contributor can follow the process without guessing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100