git-bug does not load custom ssh configuration

Labels: area/ssh kind/bug lifecycle/rotten priority/important-soon

Timeline

Martin Lindhe (martinlindhe) opened (edited)

I have a git repository on a ssh server that doesnt run on the default port 22.

It is configured with a Port entry in my ~/.ssh/config file, so the normal "ssh" command and the "git" command works:

Host srv
    Port 1234

The git remote just looks like this: "user@srv:repo"

Doing "git push" works, but trying to do a "git bug push", I end up with the following:

❯ git bug push
Error: dial tcp 192.168.1.5:22: connectex: No connection could be made because the target machine actively refused it.

I think it's an issue with a dependency. (running in Windows & PowerShell)

Martin Lindhe (martinlindhe) commented

Nevermind, it seem to be unrelated issue.

Martin Lindhe (martinlindhe) closed the bug

Martin Lindhe (martinlindhe) commented

Actually, I am at loss. Can not seem to use any port except 22.

I just tested on macOS, and get a similar error:

Error: dial tcp 192.168.1.5:22: connect: connection refused

Martin Lindhe (martinlindhe) opened the bug

Michael Muré (MichaelMure) added label go-git

Dee Anzorge (DeeUnderscore) commented

Another workaround for this is to explicitly specify the port in your git remote, for example ssh://git@example.com:1234/somerepo.git. This seems to work with both git-bug and regular git.

github-actions (github-actions) added label lifecycle/stale

sudoforge removed label go-git

github-actions (github-actions) added label lifecycle/rotten

github-actions (github-actions) removed label lifecycle/stale

github-actions (github-actions) removed label lifecycle/dormant

sudoforge changed the title from git-bug does not load custom ssh configuration to git-bug does not load custom ssh configuration

sudoforge added label kind/bug

sudoforge added label priority/important-soon

sudoforge added label area/git

sudoforge removed label area/git

sudoforge added label area/ssh