You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Give the user notice when working with remotes (i.e., using the SSH key) #205
My SSH keys are sk-ssh-ed25519. I need to touch my YubiKey every time1 I use them. My first time using cherry_picker, I resolved the conflict and ran cherry_picker --continue. At this point, it went to push the branch, but I didn't know that because there was no indication, and I didn't notice my YubiKey blinking for input. So my SSH agent timed out, the push failed, and I ran into #78.
It would be nice to give the user a notice when a fetch or push is happening so they have context for any SSH agent prompts they need to deal with, whatever those are.
Footnotes
not literally every time but the details aren't important ↩
I'm happy to follow prevailing style but my first suggestion for the core messages would be just: "Fetching from Git remote upstream" and "Pushing to Git remote origin" where the remote names follow the command line options. The SSH agent could ask for all kinds of wacky things depending on the user's setup and I don't think it's reasonable for cherry_picker to try to describe them all. I think it just needs to say what it is doing. For users in the common case it will just be a status update message, and for users with more sophisticated setups they're expected to understand how to use this information.
Activity
StanFromIreland commentedon Nov 9, 2026
Hmm, do you have a proposed format for the warning?
brettcs commentedon Nov 9, 2026
I'm happy to follow prevailing style but my first suggestion for the core messages would be just: "Fetching from Git remote upstream" and "Pushing to Git remote origin" where the remote names follow the command line options. The SSH agent could ask for all kinds of wacky things depending on the user's setup and I don't think it's reasonable for cherry_picker to try to describe them all. I think it just needs to say what it is doing. For users in the common case it will just be a status update message, and for users with more sophisticated setups they're expected to understand how to use this information.