Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't create a new git branch #68679

Closed
ynwd opened this issue Feb 14, 2019 · 10 comments
Closed

Can't create a new git branch #68679

ynwd opened this issue Feb 14, 2019 · 10 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@ynwd
Copy link

ynwd commented Feb 14, 2019

  • VSCode Version: 1.31.1 (1.31.1)
  • OS Version: MacOS Mojave 10.14.3 (18D109)
@kieferrm
Copy link
Member

Please provide the concrete steps to reproduce the problem. Thanks!

@kieferrm
Copy link
Member

/needsMoreInfo

@vscodebot vscodebot bot added the info-needed Issue requires more information from poster label Feb 15, 2019
@vscodebot
Copy link

vscodebot bot commented Feb 15, 2019

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

Happy Coding!

@raldred
Copy link

raldred commented Feb 28, 2019

@ynwd @joaomoreno
I think this could be because the behaviour of the "create new branch" option has changed recently.
After entering a branch name and pressing enter the user is now presented with a second list to select select the ref in which to base the branch from. On quick glance it's easy to see the confusion.

Creating a new branc

Looks like wording as been improved here
vldmrkl@1148298

I still think it's confusing and and unnecessary step for the majority of user who just want to branch from their current HEAD.

@Markus-bt
Copy link

Took me quite a while and several branches, created on command line to find the solution to my confusion here.
As a quick help for users, I would suggest, to change the first entry "HEAD" to something which better indicates the second use of this menue like "DERIVE FROM... HEAD

@joaomoreno
Copy link
Member

The quick open mentions "Select a ref to create a new branch from".

I'll close this and see whether more users hit this confusion. It might just be a small "getting used to it" bump.

@raldred
Copy link

raldred commented Mar 14, 2019

@joaomoreno I believe the requirement to select the ref is an unnecessary step for the majority of users. I think VScode should by default support the most common path first.

I'm pretty sure I'm not alone in saying that I have NEVER found myself wanting to create a branch from anything else other than HEAD

@Markus-bt
Copy link

I didn't even recognize that quickref...
I did not expect anything to stand there except stuff I already knew so I wasn't looking (User Expectancy)
We do several branches that depend on other branches, but we usually opened the correct branch and then created a new one. So, getting used to it.
Closing is OK, but there are at least two other issues with this theme, I think.
..and we shouldn't keep writing comments in a closed issue, so that's all from me.

@joaomoreno
Copy link
Member

@raldred @Markus-bt Addressed in #70812

@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants