BitBucket importer chooses incorrect GitLab default branch
Summary
When the Trosnoth video game repository was imported from BitBucket, the GitLab default branch ended up as branches/camp
instead of branches/default
. While this was easy to subsequently correct by changing the settings of the Trosnoth project, one would normally expect the importer to select default
as the default branch (provided it exists).
This is presumably related to #126 (closed).
Steps to reproduce
Run the BitBucket importer on the Trosnoth BitBucket repository. Check what the GitLab default branch is.
What is the current bug behavior?
The GitLab default branch after import is branches/camp
.
What is the expected correct behavior?
The GitLab default branch after import should be branches/default
.