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

Incorrect branch name when no commits exist on new repo #1428

Closed
mbomb007 opened this issue Mar 16, 2021 · 2 comments
Closed

Incorrect branch name when no commits exist on new repo #1428

mbomb007 opened this issue Mar 16, 2021 · 2 comments
Assignees
Labels
bug Something isn't working needs-verification Request for community verification
Milestone

Comments

@mbomb007
Copy link

mbomb007 commented Mar 16, 2021

  • GitLens Version: 11.3.0
  • Git Version: 2.30.0
  • VSCode Version: 1.54.3
  • OS Version: Windows 10 version 2004, using WSL2

Steps to Reproduce:

  1. Set your default branch name to something other than "main"
  2. Create a new Git repo by running git init
  3. There are files to commit but no commits
  4. In the Source Control bar, the box at the top to type a commit message correctly states your branch name, which matches the branch you are on, shown with git status. E.g. Message (Ctrl+Enter to commit on 'master')
  5. However, the COMMITS tab has an indicator that says the branch, and it says main to the right of the word "COMMITS", regardless of your Git init.defaultbranch setting. I have the setting set to something different from main in both WSL and Windows. The name will only be shown incorrectly until a repo is cloned, then it becomes correct.
@mbomb007 mbomb007 added potential-bug triage Needs to be looked at labels Mar 16, 2021
@eamodio eamodio added bug Something isn't working and removed potential-bug triage Needs to be looked at labels Apr 7, 2021
@eamodio eamodio self-assigned this Apr 7, 2021
@eamodio eamodio added this to the Soon™ milestone Apr 7, 2021
@eamodio eamodio closed this as completed in 1b6feab Apr 7, 2021
@eamodio eamodio added needs-verification Request for community verification pending-release Resolved but not yet released to the stable edition labels Apr 7, 2021
@eamodio
Copy link
Member

eamodio commented Apr 7, 2021

Can you please verify this fix in tomorrow's insiders edition?

You can install the insiders edition from here. Be sure to disable/uninstall the stable version of GitLens first.

@eamodio eamodio removed the pending-release Resolved but not yet released to the stable edition label Apr 9, 2021
@eamodio eamodio modified the milestones: Soon™, Shipped Apr 9, 2021
@github-actions
Copy link

github-actions bot commented May 9, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working needs-verification Request for community verification
Projects
None yet
Development

No branches or pull requests

2 participants