Issu in levels 4, 16 and so: what you should do about githug HOT 3 OPEN

Level 19, 20, 23, 26, 34 and more. When starting it should say to name the main branch "master" to avoid these problems

from githug.

Use this command to change the default branch name to master for all levels. You only need to run this once.

git config --global init.defaultBranch master
githug reset

All levels will now use master as the default branch.

from githug.

If I run the command

git config --list

I obtain one line reading, for example

init.defaultbranch=main

though it could be master, or any_name_you_like. As tested in Linux Debian 13/trixie, as well as from Git Bash in an instance of Windows, this variable's value equally is accessible by

git var GIT_DEFAULT_BRANCH

Thus I think this might resolve githug's problem (on some OSes/setups) with questions 4, 16, 19, 20, 23, 26, 34, etc. so far "patched locally" running git branch -m master: i) read out its value from the host, and eventually ii) let githug set up the principal branch with this name (by default). This edit of the code base would provide enough modernization to warrant the update to 0.6.0 suggested in #345.

To me, this were more promising than to edit the hints to the corresponding questions in line of (for instance level 4/file commit.rb):

hint do
  puts "You must include a message when you commit. If not working, adjust the branch's name by `git branch -m master`."
end

from githug.