GitLab also changed a few years back. We host our own, so got the update later than people using the service … it was a bit of an argument at first since everyone wanted to stick with the familiar, but laziness won out. Unfortunately, it’s not really justifiable to go back and change legacy projects, so now it’s inconsistent

[–] throwwyacc@lemmynsfw.com 1 points 8 months ago (1 children)

If you don't have any scripts that rely on branch name it should be pretty trivial actually. But I wouldn't be shocked if you had a few dozen scripts that nobody has looked at in the last century lol

[–] AA5B@lemmy.world 1 points 8 months ago

The question actually came up for a new tool to help automate dependency updates. Do we need to change the config to account for the inconsistency?

It turns out we don’t: it correctly uses the default branch, no matter what it’s called. However we had to consider the question. and investigate. It spent someone’s time