push: abort with an error when no bookmarks or tags exist
Previously, we would simply invent a master bookmark when this occurred, but in the specific case where the remote is empty. I believe that's actually unhelpful in the long run: Should a user not know about bookmarks, the first push will succeed, and subsequent pushes then not do anything. How did that bookmark get there? Instead, we should trigger a hard error for this case; that way, we'll hopefully cause the user to take a step back and find out how the command really works.
parent
1c9ac8cf90f4
No related branches found
No related tags found
Showing
- hggit/git_handler.py 5 additions, 21 deletionshggit/git_handler.py
- tests/test-gitignore-share.t 1 addition, 0 deletionstests/test-gitignore-share.t
- tests/test-push-authors.t 1 addition, 0 deletionstests/test-push-authors.t
- tests/test-push-phases.t 1 addition, 0 deletionstests/test-push-phases.t
- tests/test-push.t 8 additions, 7 deletionstests/test-push.t
Loading