Repository navigation
Excuting "gh browse gh browse -c -R owner/repo" inside another repo workspace uses the last commit of the workspace repo #4715
Description
Describe the bug
When executing gh browse gh browse -c -R owner/repo inside the work tree of another repo uses the last commit of the workspace repo:
Example
➜ gh-learning git:(master) ✗ gh browse -c -R ULL-MFP-AET-2122/static-generator-angel-ramallobenitez-alu0100312898 -n
https://github.com/ULL-MFP-AET-2122/static-generator-angel-ramallobenitez-alu0100312898/tree/a27a1db2a3a10fae176024bf13444f27af44c7d0/gh-learning
That is the last commit of the current repo:
➜ gh-learning git:(master) ✗ git log -n 1
commit a27a1db2a3a10fae176024bf13444f27af44c7d0 (HEAD -> master)
Author: Casiano Rodriguez-Leon <[email protected]>
Date: Fri May 14 11:08:29 2021 +0100
Auto-commit
Of course if we omit the -n option we get the 404:
Expected behavior
It has to use the last commit of the repo specified in the command line argument -R owner/repo
Activity
mislav commentedon Nov 23, 2021
Thank you for reporting! Good catch; and I agree with your assessment. Since you've specified a repository using the
-Rflag, we should't pay attention to the local git repo anymore, but we erroneously still do.despreston commentedon Nov 24, 2021
Is it possible to run a git command against a remote repo? I know you can specify
-Cwith some commands to point to a different local directory, but that doesn't let you run against a remote repo afaik. Would be nice to fix this without having to use the GH api to get the last commit SHA.mislav commentedon Nov 25, 2021
@despreston No, to solve this we would have to take one of the following approaches:
-cwas used with--repo; orfixes cli#4715, users can now open the last commit of a repo differen…