Skip to content

bug: multiple remote setup for reviewing pull requests #58

Closed

Description

@kakkoyun

What happened?

I tried to review an open-source project pull request, however, it doesn't manage to recognize the pull requests.

The GitHub workflow, usually suggests to maintain your own fork as origin and have an upstream where you would have actual PRs open against.

origin  git@github.com:kakkoyun/opentelemetry-go-compile-instrumentation.git (fetch) [blob:none]
origin  git@github.com:kakkoyun/opentelemetry-go-compile-instrumentation.git (push)
upstream        git@github.com:open-telemetry/opentelemetry-go-compile-instrumentation.git (fetch)
upstream        git@github.com:open-telemetry/opentelemetry-go-compile-instrumentation.git (push)

In this setup, Diffity would NOT recognizes or refreshes pull requests.

Steps to reproduce

  1. Open a project
  2. Make sure it has multiple remote setups
  3. Try to review a PR in a remote where it's not named origin

What did you expect to happen?

I would have expected it to recognize this pattern and list all the open PRs from different remotes. Or we need to have a settings to check target remote to pull the pull requets.

Diffity version

0.15.0

macOS version

26.7.1

Chip

Apple M4 Max

Logs or screenshots

Image

Activity

  1. nilbuild commented on Oct 14, 2026

    @nilbuild
    Owner

    Fixed in the next release. It now finds pull requests on upstream when origin is your fork. Your own PRs check out on their real branch, so you can push. Let me know if anything's off once you try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions