Skip to content

Back Up to GitHub

Your projects are real code, and they’re yours — push them to your own GitHub account whenever you like.

Sync to Plyed and GitHub backup both use Apple’s git tool. The first time on a new Mac, you may see a system prompt to install the command line developer tools — see Install & Sign In.

Git — connect GitHub, pick a branch, push a snapshot.

Click Git in the top bar to open the sync panel. It has two tabs:

  • Plyed — on by default. Signed-in projects sync to a Plyed-hosted remote with no setup: no token, no repository to create. This is what keeps a project’s history safe and lets features like cloud agent runs work with your code. There’s nothing to configure here beyond picking a branch name and hitting Sync to Plyed.
  • GitHub — push to a repository in your own account instead. The rest of this guide covers that tab.

Switch to the GitHub tab. The first time, you’ll connect with a personal access token:

  1. Follow the personal access token link — it opens GitHub with the right settings pre-filled (repo scope).
  2. Generate the token, copy it, paste it in, and hit Connect.

The token is stored privately on your machine. disconnect removes it — this only affects the GitHub tab; syncing to Plyed keeps working.

With the GitHub tab open:

  1. Check the repository name — it defaults to plyed-<project-name> so your Plyed projects group together in your account. Change it if you like.
  2. Pick the branch to push. Push to GitHub (the button names the branch) pushes the branch you’re on. To push something else, type a name under New branch… and choose Create & switch (say client-review or v1), or click one of your local branches. Pushing a branch never touches the others.
  3. Push to GitHub. The repo is created private under your account if it doesn’t exist, your current files are committed to the current branch, and everything is pushed. You get a link to the repo when it’s done.

Push again any time you want a new snapshot — unchanged projects just confirm the push, no empty commits. Using a branch per milestone gives you named versions you can always go back to on GitHub. A branch that exists only on GitHub can’t be checked out until it’s on your Mac — pull or fetch it first; the list marks branches that are also on your Mac with local.