Add an upstream to forked repositories
See original GitHub issueDescription
Currently, cloning a forked repository adds an origin
remote linking to the fork on GitHub. However, there is no way to fetch changes from the parent, because no remote is added for the parent.
Version
GitHub Desktop version: 0.7.0
OS version: macOS 10.12.3 (16D32)
Steps to Reproduce
- Fork a repo on GitHub
- Clone the fork with GitHub Desktop
- Run
git remote
on the command line
Expected behavior: Two remotes are present, with origin
linking to the fork and upstream
or username-of-parent-repo
linking to the parent repo
Actual behavior: Only the origin
remote is present
Reproduces how often: Always
Issue Analytics
- State:
- Created 6 years ago
- Reactions:17
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Configuring a remote repository for a fork - GitHub Docs
Open TerminalTerminalGit Bash. · List the current configured remote repository for your fork. · Specify a new remote upstream repository that will be...
Read more >Git Forks and Upstreams: How-to and a cool tip - Atlassian
Git upstreams are key to keeping track of project changes. Our tutorial will get you started using git upstream and forks to maintain...
Read more >What does 'git remote add upstream' help achieve?
"Upstream" is a name for the main repo, from where you pull and keep a clone of your fork updated, but you don't...
Read more >How To Set Git Upstream For A Respository And A Branch
Git Forked repository Upstream · You would fork the actual project repository. · Then you clone from the forked repository. · Meanwhile, to...
Read more >How to Sync and Update a Forked Repository - Section.io
To update your fork with the upstream, you need to get the remote to your local repository so that you can fetch available...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it should be automatic since they don’t have to use the remote if they don’t want to, and it shouldn’t cause any issues, unlike LFS which requires that you pay for storage space if you use too much.
I’m leaning that way too. The only case that would cause problems is if they already have an
upstream
remote configured to something else. I gotta think those cases would be vanishingly rare tho.