Skip to content

brancher: explicitly create a branch - #112

Merged
matttbe merged 1 commit into
linux-netdev:mainfrom
matttbe:brancher-refs
Oct 1, 2026
Merged

matttbe merged 1 commit into
linux-netdev:mainfrom
matttbe:brancher-refs

Conversation

@matttbe

@matttbe matttbe commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

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 <src> 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, and git didn't get updated recently.

Explicitly create a branch by passing refs/heads/.

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 <src> 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 <matttbe@kernel.org>
@matttbe

matttbe commented Oct 1, 2026

Copy link
Copy Markdown
Member Author

No need to review this I guess.

@matttbe
matttbe merged commit 52d294c into linux-netdev:main Oct 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant