How to set credentials?

[maphew]

Hi new user here. 1st impressions: very smooth and welcoming. In spite of using git for many years in a variety of settings I'm not comfortable with it. Fourchette is a breath of fresh air!

I don't see how to set credentials. While I can do whatever I want locally as far as commiting and merging etc. when I push I get "Connection refused: Credentials rejected by remote." File menu has "Git Identity" but only for setting name and email. Likewise Repo >> Settings menu is only for name and email. There are 2 pages in the user guide that mention using custom credentials but not how that is configured (1, 2) except referencing an .ssh key file.

Using VS Code and it's git extension on this same repo pushing "just works", so the credentials are set here, somewhere. It's been awhile so I don't remember specifically how I established them, and it was smooth enough that I didn't feel compelled to write a note of how it was done; ~.ssh/ is empty.

Fourchette is 1.2.1 Flatpak.
Host is Bluefin-dx atomic desktop (Fedora 41).

[jorio]

Welcome, and I'm glad your first impressions were positive :)

When connecting to an SSH remote, GitFourchette normally attempts keys from your ~/.ssh directory until it finds one that works. If you've stored your keys elsewhere, we need to find out where they are.

The ssh -vT command can tell us the key that vanilla git uses to connect to your remote. For example, if your remote's full URL looks like git@github.com:jorio/gitfourchette.git, you can run ssh -vT git@github.com. The relevant part of the output is this:

debug1: Offering public key: /home/u/.ssh/id_ed25519 ED25519 SHA256:...
debug1: Server accepts key: /home/u/.ssh/id_ed25519 ED25519 SHA256:...
Authenticated to github.com ([140.82.121.3]:22) using "publickey".
...
Hi jorio! You've successfully authenticated, but GitHub does not provide shell access.

The Server accepts key line tells us that /home/u/.ssh/id_ed25519 was the key that worked. Once you have that path, return to GitFourchette, right click the remote in the sidebar, select "Edit Remote", tick "Log in with custom key file" and select the key file. Please let me know if that worked or if we should try something else.

[maphew]

ah, maybe that's it, does Fourchette only use ssh remotes?

I'm using https andgit-credential-oauth, which authenticates via browser on first use in the repository. Running git push in terminal from a repo I've already authenticated works fine, but Fourchette in the same repo fails.

[jorio]

Ah, yes, that's not supported at the moment, unfortunately. Under the hood, GitFourchette is independent from git itself (it uses libgit2), so authentication with remotes is more bare-bones. This is proving to be inconvenient for use cases like yours (and others like #8).

To overcome these limitations, I'm thinking of driving git itself for operations that need to auth with the remote. I can let you know in this thread if/when I get around to implementing this in a future release. Sorry for the inconvenience in the meantime!

[maphew]

Thanks for confirming and the extra info. I can get by with flipping to shell for a git push now and again. Eventually I'll get irritated enough to relearn how to set up a stored ssh key. ;-) For now it's good enough that I understand how things are structured.