Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Master branch is created in converted repo even if it does not exist in the initial repo #41

Open
lavinia8 opened this issue May 12, 2017 · 0 comments

Comments

@lavinia8
Copy link

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>.

❓ 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant