-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Description
CLI Feedback
What was confusing or gave you pause?
I noticed that there is an inconsistency in the naming behavior of remote repositories created by the gh repo fork and gh pr create commands.
when using gh repo fork, the origin remote repository is renamed to upstream by default, and the fork created is named origin.
However, when using gh pr create, the forked remote repository is directly named fork.
I believe this inconsistency may cause confusion, and it would be more user-friendly to unify the naming behavior of these two commands.
Suggestions:
Align the naming behavior of the forked remote repository created by gh pr create with gh repo fork, by naming it origin for consistency.
Such unified behavior would improve user understanding and usage of the gh command-line tool, and help avoid confusion and mistakes.
I would be happy to submit a pull request to implement this feature, if you think it's feasible. I have identified the relevant implementation in the source code.
Thank you for considering this suggestion!