lindell / lindell/github-release-cli
Custom branch tagging
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently the script doesn't allow to tag a branch that isn't the default one(master). In order that to happen, a user must include `target_commitish` as a parameter when creating the release. More info can be found [here](https://developer.github.com/v3/repos/releases/#create-a-release).
I'd help with a PR but I don't really know Go and really don't have time at the moment. Really appreciated the help with the script.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the release-creation request in the Go CLI and compare its parameters with the linked GitHub Releases API documentation. Done means a user can provide a non-default branch through target_commitish and the resulting release is tagged from that branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100