GitLab default branch: using an empty default when not set yet
As the comment explains, this is for now the only way to let the Rails app actually know that the default branch hasn't been set yet. After a lot of defaultings in the applicative code, this eventually activates the code that's responsible for actually setting it while receiving the first push. We can do something much more robust and maintainable, but that will be after the first push. Meanwhile, we do have functional tests about that to cover our backs.
topic/default/hpd-0-17-fixes in 1 minute and 24 seconds4 jobs for