GitLab default branch: new logs to investigate problems
We keep getting reports that on some projects the default GitLab branch gets overwritten to point to a topic (heptapod#714), which is obviously very wrong. It is not clear how this really happens, perhaps these new logs will help. The case of `None` creeping in was reported by Alphare in the matrix channel. He stumbled upon it while releasing Mercurial 6.7.3
parent
b48f39f2e589
No related branches found
No related tags found
Please register or sign in to comment