Default branch to is always set to "master"
See original GitHub issueDescription
When making a new branch, the default selected branch is always master
even if the default branch is set to develop
or feature
on Github.
Version
- GitHub Desktop:
1.6.2
- Operating system:
Mac OS 10.14.2
Steps to Reproduce
- create a new branch from github desktop
- the default selected branch is always master
Expected Behavior
Uses the default branch setting from the Github settings for the repo.
Actual Behavior
It’s always using master
as the default branch to create branches off instead of the actual default branch setting from Github.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
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 >The new Git default branch name - GitLab
Every Git repository has an initial branch, which is the first branch to be created when a new repository is generated. Historically, the ......
Read more >Why GitHub renamed its master branch to main | TheServerSide
Since its inception, the Git DVCS tool's default branch name was set to master. Every Git repository had a master branch unless a...
Read more >5 steps to change GitHub default branch from master to main
Step 1 - Move the 'master' branch to 'main' · Step 2 - Push 'main' to remote repo · Step 3 - Point...
Read more >git how to change default branch for everything I do?
Following the FAQ article "How to Rename the master branch to main in Git", and the GitHub documentation itself, you can:.
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
@Eyesonly88 as a workaround you can clone a fresh copy of the repository, which should cause the correct default branch to be recognized (I just tested this behavior). Let me know if that doesn’t work for you.
Hello guys, it seems for me that the solutions above are not working the only solution i found to corect it was to re-clone the repo. so the issue remain Open
and yes i tried all the mentionned solution even reloading the repo