New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support different default OWNER in gh repo clone REPO
#2000
Comments
This comment has been minimized.
This comment has been minimized.
I definitely see the merits in this for folks using GH at work under a single organization; I'm marking as |
I would love for this to be configurable using an environment variable (as well). My use case is that I'm a member of multiple organizations and the directory structure on my machine mirrors that of the |
I'd like to +1 this issue. I love the idea of having a fallback organization from which to clone repos, i.e. if I run |
We're cool with a new config added for this. Let's call it |
This comment was marked as spam.
This comment was marked as spam.
A hack but this works for me rn:
Then you can do
|
Made a PR that would query for the repository in the user's organizations as a fallback, this would solve my problems for this issue. |
Describe the feature or problem you’d like to solve
The feature to have the authenticated user as default OWNER when clone the repo is very neat, but for some people that could not be enough. For example for people that work a lot inside of a specific organization could be nice to set a different default owner
Proposed solution
using the gh config we could set a default owner, like gh config owner acme
Then every time we use the gh repo clone we don't need to specify the owner
The text was updated successfully, but these errors were encountered: