Skip to content
Snippets Groups Projects
Commit 78cbae27e974 authored by Dan Villiom Podlaski Christiansen's avatar Dan Villiom Podlaski Christiansen
Browse files

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
1 merge request!124Adjust initial clone and push behaviour
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment