Topics as Heptapod default branch: avoid some surprises
This fixes the scenario of heptapod#1716 in two different ways: - we do not change the default Heptapod branch from one topic to another if not needed. - we check if the topic of the existing default branch has become obsolete and force switching in that case. Then we add some protections against the case where the changes prune the default branch and provide no suitable replacement (such as in pruning the whole topic), so that momentary persistence of the GitLab branch does not shadow the fact that an obselete changeset is being references (this the end cause of the HTTP error 500 anyway).
parent
1dae3eaa6837
No related branches found
No related tags found
Showing
- hgext3rd/heptapod/state_maintainer.py 31 additions, 0 deletionshgext3rd/heptapod/state_maintainer.py
- hgext3rd/heptapod/tests/no_git/test_inner.py 37 additions, 1 deletionhgext3rd/heptapod/tests/no_git/test_inner.py
- hgext3rd/heptapod/tests/no_git/test_integration.py 51 additions, 0 deletionshgext3rd/heptapod/tests/no_git/test_integration.py
Please register or sign in to comment