question-mark
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.

display PRs from upstream repository in your fork

See original GitHub issue

I am the maintainer of Zebobo5/Vlc.DotNet. I mostly work on my fork, and make PR to integrate changes to the main repository.

To avoid pushing inadvertently bad code into Zebobo5’s project, I cloned my fork (which is origin), and added an upstream remote to track changes to the main project (git pull upstream develop)

I’ve always done everything from CLI, but wanted to give GitHub desktop a try, to see if it could improve my workflow. It seems that GitHub desktop doesn’t understand this workflow, and doesn’t let me checkout the PR from the main project.

My question is: Is there a way to checkout a specific PR from the main project while on a fork?

Ideas:

  • Show PR from this project + from the original fork in a separate category
  • Show PR from all remotes configured

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
ampinskcommented, Mar 17, 2020

Based on what we decided in #9170, we’re going to default to showing the pull requests from the parent repository, but with an indicator (in the form of a list header) to make that explicit.

pull-request-list
2reactions
jeremyVignellescommented, Dec 10, 2018

That would be an alternative but I find it unpractical for a few reasons :

  • A mistake has been made a long time ago : vlc has been checked in git, so the repo is quite heavy, I’d need to shallow clone
  • Switching between repo would be a source of mistakes
  • Each sample in this repo installs a copy of vlc from NuGet, which represents a lot of space (my repo folder is currently 4.06GB ), so doubling would be a waste of space.

I don’t thinks this would be a viable solution for large repos like dotnet/coreclr

Read more comments on GitHub >

github_iconTop Results From Across the Web

git - How to apply unmerged upstream pull requests from other ...
Ignore the original repo and go directly to the fork that made the pull request. You want to manually pull the commit the...
Read more >
pull | Keep your forks up-to-date via automated PRs
Pull requests are created when upstreams are updated. Automatically merge or hard reset pull requests to match upstream. Add assignees and reviewers to...
Read more >
Fork a GitHub Repository & Submit a Pull Request - Jake Jarvis
Walkthrough of forking a GitHub repository, cloning it, committing your changes to a new branch, and pushing it back upstream.
Read more >
Fork your repository - Azure Repos | Microsoft Learn
Share code between forks. The original repo is often referred to as the upstream repo. You can create PRs to merge changes in ......
Read more >
How to Synchronize Your GitHub Fork - DevDojo
Synchronizing the fork with the upstream repository. The first thing you want to do is to navigate to the directory of the project...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found