Custom branch tagging

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli, release

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.

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.
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.

Dominant language
Go
Stars
11
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lindell/github-release-cli

All issues in lindell/github-release-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.