Fork Sync
In one sentence
Fork Sync was planned as an app that keeps a derived GitHub repository (a fork or a customised edition) up to date with its base repository; in the code I reviewed it is retired and not available as a hosted app.
What makes it unique
There is nothing live to describe. The design on paper promised to bring in base changes while respecting deliberate differences, stop for a human when a base change breaks something the derived repository depends on, check that the result builds, and open a pull request. The worker behind the page was only an empty shell before it was removed.
When to use it / when not to
- Do not look for it on the hosted pages. The page, controller, task and worker were removed in the latest cleanup, and its slot in the plugin list is marked "Retired".
- For keeping dependencies fresh → NuGet Updater.
- For understanding what the base project is → Code Graph and Repo Docs.
- For splitting oversized classes → Refactor Assistant.
Before you start
Nothing to prepare. If you are asked to sync a fork, use your Git host's own tools (merge or rebase from the upstream remote) and review conflicts by hand.
Step by step
- Do not rely on a hosted Fork Sync page.
- Use Git directly for the merge.
- Afterwards, run NuGet Updater in report mode to see package drift, and Repo Docs to regenerate documentation.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| (none) | The app is retired | – | See alternatives above |
What you get
Nothing from this app.
Quality & limits
Not applicable. Any page text that suggests Fork Sync is available should be treated as out of date until verified on the live app.
Works well with
- Use instead: NuGet Updater, Code Graph, Repo Docs.
Common mistakes & fixes
- Expecting an automatic merge of a fork → no hosted Documentize app does this.
- Expecting Repo Docs to merge anything → it only writes generated documentation files.
Same thing elsewhere
Not verified. See channels.
Try it
Check your own fork: list the commits you are behind with your Git host, then run NuGet Updater with Report only on the base repository to see which package updates the base is waiting on.