There will be about 1h of downtime on 2020-03-02 at 13:00 UTC+1 (change of servers and upgrade to Heptapod 0.20.0 final)

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.
4 jobs for topic/default/hpd-0-17-fixes in 1 minute and 24 seconds
Status Job ID Name Coverage
  Main
passed #120240
tests-current

00:00:34

100.0%
 
  Compat
passed #120241
check-sdist

00:00:30

failed #120243
allowed to fail
tests-hg-default

00:00:41

99.0%
passed #120242
tests-hg-stable

00:00:49

100.0%
 
Name Stage Failure
failed
tests-hg-default Compat
FAIL Required test coverage of 100% not reached. Total coverage: 99.80%
=========================== short test summary info ============================
FAILED hgitaly/service/tests/test_commit.py::test_is_ancestor_obsolete - Type...
FAILED hgitaly/service/tests/test_repository_service.py::test_has_local_branches
FAILED hgitaly/tests/test_revision.py::test_gitlab_revision_changeset_by_hex
=================== 3 failed, 39 passed, 1 warning in 6.10s ====================
Running after_script
Uploading artifacts for failed job
ERROR: Job failed: exit code 1