Repository navigation
add a local switch so it is easy to check local tickets etc #790
Description
Activity
Hi, if you clone a project locally and change the current directory of your shell into it:
cd learn-go-with-testsMost GitHub CLI commands without any extra arguments like
gh issue listwill by default query resources from the GitHub repository that the local repo is a clone of:gh issue list #=> shows issues from the 'quii/learn-go-with-tests' repoHowever, when you are in a local project that is a fork, we will still query the parent repo (
quii) by default. Is your feature proposal to queryms4720/learn-go-with-testsinstead? Any clarification would be helpful. Thank you!See also #350 for past discussion
yes checking local tickets, the tickets I made for the ms4720 repo
Gotcha, thanks!
Right now your only option is to be explicit about every operation as to which repo do you want to query:
gh issue list -R ms4720/learn-go-with-testsbut I understand that this is repetitive, since you will always prefer to look up the data in your own fork.
gh now asks about what repo to use for issue queries; i'm going to close this in the hopes that that suffices but if not we can continue discussion and reopen
Describe the feature or problem you’d like to solve
easy viewing of local repo issues and maybe other things
I forked quii/learn-go-with-tests to ms4720/learn-go-with-tests and would like a simple way to say use local repo resources like tickets, I made a ticket for each chapter and a couple of milestones for the project
Proposed solution
add a -l and/or --local switch so you just use local resources
How will it benefit CLI and its users?
just much simpler than -R ms4720/... when I am in the local repo
Additional context