Tiny annoyance where if you try to lumen diff 1111 it'll rely on gh repo view own origin parsing logic, and it seems like it'll always default to upstream. Let's say you're in a fork, and there's a #1111 PR both upstream AND in your fork. Even tho you're checked out in your fork origin, lumen diff 1111 will fetch the upstream's PR.
Steps to reproduce:
- create repo A
- fork repo (now repo B)
- create
#1 pr on repo A
- create
#1 pr on repo B (the fork)
- checkout repo B
lumen diff 1
- notice how it'll show the diff for repo A
Tiny annoyance where if you try to
lumen diff 1111it'll rely ongh repo viewown origin parsing logic, and it seems like it'll always default to upstream. Let's say you're in a fork, and there's a#1111PR both upstream AND in your fork. Even tho you're checked out in your fork origin,lumen diff 1111will fetch the upstream's PR.Steps to reproduce:
#1pr on repo A#1pr on repo B (the fork)lumen diff 1