Enable matching of repo structure during clone #11902
Conversation
|
Hi! Thanks for the pull request. Please ensure that this change is linked to an issue by mentioning an issue number in the description of the pull request. If this pull request would close the issue, please put the word 'Fixes' before the issue number somewhere in the pull request body. If this is a tiny change like fixing a typo, feel free to ignore this message. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
Thank you for your pull request! 🎉 This PR appears to fix the following issues that are not labeled with
help wanted
As outlined in our Contributing Guidelines, we expect that PRs are only created for issues that have been labeled While we appreciate your initiative, please note that:
What happens next:
Thank you for your understanding and contribution to the project! 🙏 This comment was automatically generated by cliAutomation. |
When creating a repo clone, it's often convenient to match the org with the repo name.
During a normal
gh repo cloneoperation, and wanting to contribute to various CLI repo, you would default to the code attempting to be checked out in the sameclidirectory.e.g.
gh repo clone cli/cligh repo clone npm/cligh repo clone httpie/cliTrying to run any of the above commands in a common
~/go/src/github.comdirectory would result in the following error:You can obviously pass your own repo name, but it can get quite verbose to type (aka https://github.com/react-native-community/cli)
This PR adds the
--matchflag, allowing for a simple flag to indicate your desire to match the owner/repo dir structure.going from:
to then having to be explicit:
to what you were trying to do in the first place:
Fixes #11904