Skip to content

Give the user notice when working with remotes (i.e., using the SSH key) #205

Closed

Description

@brettcs

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

  1. not literally every time but the details aren't important ↩

Activity

  1. StanFromIreland commented on Nov 9, 2026

    @StanFromIreland
    Member

    Hmm, do you have a proposed format for the warning?

  2. brettcs commented on Nov 9, 2026

    @brettcs
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions