You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the first automated commit, if the default branch name in standardly code generator is "main" and the local git init default is set to "master", there are nasty, dirty pushes to github.
The text was updated successfully, but these errors were encountered:
Spectralgo
changed the title
VIEW: Add Warning Or Disclaimer For Having Git Init Default Head Branch Set To Master Instead Of Main
VIEW: Add Warning Or Disclaimer For Having Git Init Default Head Branch Set To Main Instead Of Master
Jul 21, 2022
Spectralgo
changed the title
VIEW: Add Warning Or Disclaimer For Having Git Init Default Head Branch Set To Main Instead Of Master
VIEW: Add Warning Or Disclaimer For Having Git Init Default Head Branch Set To Master Instead Of Main
Jul 21, 2022
@Spectralgo@coeur85 GitHub CLI does not currently offer a command to check the default branch name so it would not be possible to do that check at the moment to do this validation.
GitHub uses main by default. If you are creating your repo via Visual Studio and this is setting up the branch as master then you could run this command to ensure Visual Studio uses main next time.
On the first automated commit, if the default branch name in standardly code generator is "main" and the local git init default is set to "master", there are nasty, dirty pushes to github.
The text was updated successfully, but these errors were encountered: