Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
[WIP] Experimental feature: synchronize forks #966
Closed
Conversation
When you fork a repo, it's hard to keep it in sync with the upstream repository. This experimental feature goes through all the remote branches of a configured "upstream" remote, grab all local branches which match by name, have not diverged in history but are behind the upstream remote branch, updates the local branches via a fast forward fetch, and pushes the updated local branches to the "origin" remote, so that the fork is synchronized on the server with upstream.
|
@shana Is this the Fork PR you will pick up again after GDC? Or is this an older one that should be closed? |
|
Too many conflicts! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
When you fork a repo, it's hard to keep it in sync with the upstream repository. This experimental feature goes through all the remote branches of a configured "upstream" remote, grab all local branches which match by name, have not diverged in history but are behind the upstream remote branch, updates the local branches via a fast forward fetch, and pushes the updated local branches to the "origin" remote, so that the fork is synchronized on the server with upstream.
This is a really really old branch that's been lying around. The button is in Team Explorer Home which is probably not the best place (probably in Connect? Context menu somewhere? unsure), and I'm sure it needs some cleaning up.