Skip to content

Allow setting a default push target for pr create #1718

@mislav

Description

@mislav

In #1706 we've changed pr create so it no longer automatically pushes to a remote, but prompts instead. We made that change because, during beta, we weren't able to find a default that people would be generally satisfied with. Some people always want to push to their fork, some always want to push to the base repo even though they might have a fork, and some want to avoid auto-pushing altogether. Finally, for people working on work or otherwise private projects, it doesn't make sense to ask for a push target because there is usually only one, centralized target.

The new change adds an extra step to pr create that some people might find tedious and repetitive, especially when they already know up front that they always want to push to the same remote. We could either, or both

  • Allow explicitly setting a default push target. I imagine this setting should be per-repository instead of global;
  • After the user chooses a push target for the first time, we could remember it and automatically choose it the next time. Although, this could potentially be surprising and unwanted on subsequent pushes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    coreThis issue is not accepting PRs from outside contributorsenhancementa request to improve CLIgh-prrelating to the gh pr command

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions