Version History & GitHub
Save versions of a score, try ideas on branches, merge them back, and keep it all on GitHub.
Versions and branches
In the score editor, tap History. Save Version keeps a snapshot you can go back to. Saving in the editor also records one. New Branch starts a separate line of edits, from now or from any earlier version, so you can try something without touching the main score.
Roll Back to This Version restores an earlier snapshot as a new version, so nothing is lost and you can undo the roll back. Switching branches first saves your unsaved edits.
Merge brings another branch into the current one, bar by bar. A bar changed on only one branch comes across; a bar changed on both clashes, and you choose to keep yours or take theirs. Bars are matched by number, so a bar added or removed early on one branch can make the rest show as clashes.
- Save a versionIn the score editor, History and Save Version keep a snapshot you can return to.
- Start a branch to try an ideaNew Branch starts a separate line of edits from now or from any earlier version.
- Roll back to an earlier versionRoll Back to This Version restores an earlier snapshot as a new version, so nothing is lost.
- Merge a branchMerge brings another branch into the current one, bar by bar.
- Resolve merge clashesA bar changed on both branches clashes, and you choose to keep yours or take theirs.
- Connect a score to GitHubConnect a score to your own GitHub repository and push its version history there.
- Where your GitHub token is keptThe token is kept in your device's Keychain and sent only to GitHub.