Checking out a PR over SSH fails with error when SSH port is not 22 #483

9pfs commented 2026年06月01日 06:05:55 +02:00

Expected Behavior

I executed fj pr checkout 1, expecting to have the forgejo CLI add a remote, fetch the relevant commits, and check out a new branch.

Actual Behavior

Instead of checking out the branch, an error message was displayed (redacted output provided):

[USER@HOST REPOSITORY_DIR]$ fj pr checkout 1
Error: the given reference name 'refs/heads/pr-git-ssh.h.wer.ee:2222-REDACTED-1' is not valid; class=Reference (4); code=InvalidSpec (-12)
Location:
 src/prs.rs:1544:13
[USER@HOST REPOSITORY_DIR]$ 

Steps to Reproduce

Clone a repository from a forgejo instance that has an SSH server on a non-22 port, then attempt to check out a PR over SSH.

fj Version

fj v0.5.0
user agent: forgejo-cli/0.5.0 (https://codeberg.org/forgejo-contrib/forgejo-cli/)
build type: from source
 target: x86_64-unknown-linux-gnu
Check for a new version with `fj version --check`
Additional information: AUR package forgejo-cli-git, version v0.5.0.r134.g4de88bd-1

Forgejo Version

15.0.2

Code of Conduct

• I agree to act in accordance with the CoC & AI Agreement.
• This issue was not generated by an LLM, even in part.

### Expected Behavior I executed `fj pr checkout 1`, expecting to have the forgejo CLI add a remote, fetch the relevant commits, and check out a new branch. ### Actual Behavior Instead of checking out the branch, an error message was displayed (redacted output provided): ```text [USER@HOST REPOSITORY_DIR]$ fj pr checkout 1 Error: the given reference name 'refs/heads/pr-git-ssh.h.wer.ee:2222-REDACTED-1' is not valid; class=Reference (4); code=InvalidSpec (-12) Location: src/prs.rs:1544:13 [USER@HOST REPOSITORY_DIR]$ ``` ### Steps to Reproduce Clone a repository from a forgejo instance that has an SSH server on a non-22 port, then attempt to check out a PR over SSH. ### `fj` Version ```text fj v0.5.0 user agent: forgejo-cli/0.5.0 (https://codeberg.org/forgejo-contrib/forgejo-cli/) build type: from source target: x86_64-unknown-linux-gnu Check for a new version with `fj version --check` Additional information: AUR package forgejo-cli-git, version v0.5.0.r134.g4de88bd-1 ``` ### Forgejo Version 15.0.2 ### Code of Conduct - [x] I agree to act in accordance with the CoC & AI Agreement. - [x] This issue was not generated by an LLM, even in part.

LordMZTE commented 2026年06月01日 08:05:04 +02:00

I can reproduce this on my git server @ https://git.mzte.de. We can use that for testing.

I can reproduce this on my git server @ https://git.mzte.de. We can use that for testing.

Fluffinity commented 2026年06月20日 10:42:16 +02:00

Can you try setting the port in the git remote URL and tell us the result?

Can you try setting the port in the git remote URL and tell us the result?

Cyborus commented 2026年06月20日 16:16:16 +02:00

Can you try setting the port in the git remote URL

Is that not already the case It's failing because the : in the URL indicating the port isn't allowed in refspecs

> Can you try setting the port in the git remote URL Is that not already the case It's failing because the `:` in the URL indicating the port isn't allowed in refspecs

Fluffinity commented 2026年06月20日 17:04:44 +02:00

Is that not already the case It's failing because the : in the URL indicating the port isn't allowed in refspecs

I did not see the port in refs/heads/pr-git-ssh.h.wer.ee:2222-REDACTED-1. Interesting, that such a refspec gets created in the first place then.
@LordMZTE regular git operations work just fine with your server, right?

> Is that not already the case It's failing because the `:` in the URL indicating the port isn't allowed in refspecs I did not see the port in `refs/heads/pr-git-ssh.h.wer.ee:2222-REDACTED-1`. Interesting, that such a refspec gets created in the first place then. @LordMZTE regular git operations work just fine with your server, right?

LordMZTE commented 2026年06月22日 09:18:11 +02:00

@LordMZTE regular git operations work just fine with your server, right?

Yes, this is likely just a bug with how we determine the name of the new branch :D

> @LordMZTE regular git operations work just fine with your server, right? Yes, this is likely just a bug with how we determine the name of the new branch :D