From 52d294c1c2cf03a26a27121f1ac0ab5d06a86cff Mon Sep 17 00:00:00 2001 From: Matthieu Baerts Date: Thu, 1 Oct 2026 09:57:17 +0200 Subject: [PATCH] brancher: explicitly create a branch Strangely, the brancher service wasn't able to push a new branch recently: $ git push brancher HEAD:net-next-2026-10-01--03-00 error: The destination you provided is not a full refname (i.e., starting with "refs/"). We tried to guess what you meant by: - Looking for a ref that matches 'net-next-2026-10-01--03-00' on the remote side. - Checking if the being pushed ('HEAD') is a ref in "refs/{heads,tags}/". If so we add a corresponding refs/{heads,tags}/ prefix on the remote side. Neither worked, so we gave up. You must fully qualify the ref. The error makes sense, but it is strange because it always worked before. Explicitly create a branch by passing 'refs/heads/'. Signed-off-by: Matthieu Baerts --- pw_brancher.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pw_brancher.py b/pw_brancher.py index fbf3c8e0..55568b7b 100755 --- a/pw_brancher.py +++ b/pw_brancher.py @@ -327,7 +327,7 @@ def create_new(pw, config, state, tree, tgt_remote) -> None: db_insert(config, state, branch_name) log_open_sec("Pushing out") - tree.git_push(tgt_remote, "HEAD:" + branch_name) + tree.git_push(tgt_remote, "HEAD:refs/heads/" + branch_name) log_end_sec() log_open_sec("Generate deltas")