Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`git-checkout-pr` should also work in closed PR or deleted fork

See original GitHub issue

Description

It seems the exclusion is due to implementation problem: ee2d9e6 (#3596)

I agree it would be rare, but chances are people need to checkout a closed PR in order to test it, base their work on it or whatever. GitHub doesn’t hide the “Code” dropdown on closed PR so I think we shouldn’t either.

Screenshot

No response

Example URL

https://github.com/sindresorhus/refined-github/pull/3759

Issue Analytics

State:
Created 2 years ago
Comments:11 (10 by maintainers)

Top GitHub Comments

3reactions

cheap-glitchcommented, Nov 5, 2022

The current logic can be found here: ทำไมอ่าาาาา มีปัญหาเรอะ

Gotta say, this new version of TypeScript is looking a bit cryptic to me 😉

that table would also be good as a comment in the file itself

Which table?

2reactions

fregantecommented, Aug 22, 2021

```shell
git config --add remote.origin.fetch "+refs/pull/<pr number>/head:refs/remotes/origin/pr/<pr number>"
git pull origin
git switch --track origin/pr/<pr number>

Like!

Let’s ensure it’s pushable. We had some constraints when looking for the best/shortest commands, specifically to ensure that pushing also works (and maybe more). @kidonng refer to the original issue and PR.

Regarding this feature request, it makes sense for the simple reason that GitHub includes the Code dropdown on closed PRs too, so we should handle it the same way.