`git feature` not re-opening the branch on subsequent calls?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
The readme seems to indicate that subsequent calls to git feature XYZ should check that branch out. It doesn't appear to be working for me... am I doing something wrong?
$
brandon at MacMini in ~/code/myapp on master
$ git feature myfeature
brandon at MacMini in ~/code/myapp on feature/myfeature
$ git checkout master
Switched to branch 'master'
brandon at MacMini in ~/code/myapp on master
$ git feature myfeature
brandon at MacMini in ~/code/myapp on master
$
I was expecting to be on branch feature/myfeature at the end there, but am on master.
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
Start with the README section describing git feature, then locate the git feature command entry point and trace what happens when feature/myfeature already exists. Reproduce the sequence in the issue, and confirm that a subsequent call checks out the existing branch instead of leaving the repository on master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100