Vovy syncs your fork with the original repo using GitHub's Sync fork button or a local merge, resolving conflicts with your customizations.
My fork is 40 commits behind the original repo, bring in their updates
How it works
- See how far behind you are: Vovy opens your fork on GitHub and reads the banner saying how many commits you are behind and ahead of the original.
- Preview the incoming changes: Vovy summarizes the original repo's new commits as a card, and flags any that touch files you customized.
- Sync on a branch: Vovy pulls upstream into a new branch rather than main, so you can test before anything goes live.
- Resolve conflicts: Where the original changed code you edited, Vovy shows both versions and merges them with you.
- Test and merge: Vovy runs the build, opens a pull request into your main, and merges after your OK.
What you provide
- Your forked repo
- Which customizations must stay
What you get
- Your fork up to date
- Customizations preserved
- Conflicts resolved
- Changes tested before merging
FAQ
What does the Sync fork button do?
It merges the original's changes into your fork on GitHub. It works when there are no conflicts; otherwise you merge locally.
Will this overwrite my changes?
No. A merge keeps both sides and asks when they collide. Avoid Discard commits, which throws your work away.
How often should I sync?
Every few weeks, or before a big update. Small syncs are much easier than 200-commit ones.
Related tasks
All tasks