The master branch is automatically created by the conversion => this prevents the subbranches of master to be created.
Usecase:
There is no master branch in the original repository; the default one is main. There are several branches named master/<name>.
During the conversion, master is automatically created and, in the end, it points to the same commit the main branch points to. Besides that, the subbranches of master cannot be created, which leads to missing branches and dangling commits.
The workaround is to rename all the master/<name> branches to placeholder/<name>, run the conversion, delete the master branch (because in the initial repo the default is main) and rename back the branches to master/<name>.
:question: Why is master created in the converted repo since there is no master in the initial repo and why does it point to the same commit the default branch points to?
The
masterbranch is automatically created by the conversion => this prevents the subbranches ofmasterto be created.Usecase: There is no
masterbranch in the original repository; the default one ismain. There are several branches namedmaster/<name>. During the conversion,masteris automatically created and, in the end, it points to the same commit themainbranch points to. Besides that, the subbranches ofmastercannot be created, which leads to missing branches and dangling commits.The workaround is to rename all the
master/<name>branches toplaceholder/<name>, run the conversion, delete themasterbranch (because in the initial repo the default ismain) and rename back the branches tomaster/<name>.:question: Why is
mastercreated in the converted repo since there is nomasterin the initial repo and why does it point to the same commit the default branch points to?