Open eparejatobes opened 9 years ago
It's a bit more complex when the base branch for the PR is not master. I also wanted to use ghi feature for that, but it seems that its development got frozen. Anyway, a solution would be to have a part of the config stored in the repo itself, then gtm will know relationships between branches and issues and it will be shared among collaborators. WDYT?
Not a great deal, but is a bit annoying that when you want to work on a PR already in place, you normally have the issue number and you need to
it'd be nice to have something like
gtm pick <issueno>
which would basically do the above if the issue is a PR.