Skip to content

PR diffs akwardly default to upstream #151

@joaomendoncaa

Description

@joaomendoncaa

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:

  1. create repo A
  2. fork repo (now repo B)
  3. create #1 pr on repo A
  4. create #1 pr on repo B (the fork)
  5. checkout repo B
  6. lumen diff 1
  7. notice how it'll show the diff for repo A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions