GitHub Desktop show the wrong default branch
See original GitHub issueDescribe the bug
The default branch for my repo is master
. However, GH Desktop shows the default as a different branch, one that is in fact deleted.
Version & OS
GitHub Desktop 2.6.1 MacOS Big Sur, Version 11.1
Steps to reproduce the behavior
- Go to the remote repo and verify that
master
is set as the default. - Open GitHub Desktop and switch to the local copy of the repo.
- Click Current Branch to list the branches.
- See that
master
is not listed as the default.
Expected behavior
GitHub Desktop should be in synch with the settings of my remote repo.
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (6 by maintainers)
Top Results From Across the Web
Default Branch does not Update · Issue #5709 · desktop/desktop
Have a private GitHub repo with a default branch dev · Create another branch named develop · Change the settings of the branch...
Read more >Github Desktop won't update Default Branch to main #13669
Change default to main in the repository and delete master · In every conceivable place change default branch to main · Rub these...
Read more >Changing the default branch - GitHub Docs
Under your repository name, click Settings. ... Under "Default branch", to the right of the default branch name, click . ... Use the...
Read more >Wrong Default Branch Selected Locally · Issue #6608 - GitHub
Description using only GitHub Desktop i created a branch named sfdx-master from master one. there i re-structured APEX files to comply with ...
Read more >Default branch not changing · Issue #14844 · desktop ... - GitHub
Create a new repository on gitlab · Check out the repository in github desktop · Create a branch "develop" · Make the branch...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Andyroid0 you can download the latest beta to test out the fix for this issue:
https://desktop.github.com/beta
I ended up deleting the feature branch that was incorrectly marked as the default branch. That seems to have fixed the issue for me and correctly set it back to the expected master branch.