Git Repositories

Clone, pull and push Git repositories over HTTPS.

Every repository has an HTTPS address that works with Git on any computer. A token belongs to your account and works for every repository your account can read or push to, in Personal and in each of your teams. A project comes in with a push and goes out with a clone, with its commits either way.

Get started free

HTTPS access tokens

Over HTTPS, Git uses a repository access token as its password. Give a token a name, such as the computer it will be used on, and tick Read repositories to clone and pull, Write to repositories to push, or both. When Git asks for a username and password, any username works and the token is the password. Git does not accept your Magpie password.

Shown once
The full token is shown only on the page that created it, hidden until you choose Reveal. Copy token copies it without showing it. Afterwards the list shows each token's name, its first characters and its access: Read only, Write only, or Read and write.
Stored on your computer
A Git credential helper, such as Keychain on a Mac, can store the token so Git does not ask for it again.
Password Vault
With a Password Vault, Save in Password Vault opens it in a new tab with the token filled in, ready to save. The token goes from one browser tab to the other and is not sent to Magpie again.
Revoke
Revoke beside a token stops it working. Git connections that use it will be refused, and the other tokens keep working.

Moving a project into Magpie

A new repository is empty unless it was given starter files. Its page then shows the clone address first, with two sets of commands to copy. Each uses the repository's address and its default branch, main.

  1. Start a project

    The first set makes a new project on your computer with a README, commits it and pushes it.

  2. Push a project you already have

    The second, run in the project's folder, adds the repository as the origin remote, names the current branch main and pushes it with its commits.

  3. Other branches and tags

    Pushes can add and update other branches and tags. Git fetches and clones them as usual; the repository's page on the website shows main.

Cloning a public repository, and taking code out

Anyone can clone or pull a public repository over HTTPS without a token or a Magpie account. Pushing to it still needs a token with Write to repositories, from an account that can push to it.

Anyone who can read a repository can clone it with ordinary Git, with its commits, and work on that clone anywhere Git works. Deleting a repository in Magpie stops Magpie serving it; clones already on someone's computer are not affected.

A token acts as your account

A token gives no access by itself. Git can read the repositories your account can read and push where your account can push, through the repository's team and its Member access. A token without Write to repositories cannot push, even where your account can.

When your account loses access to a team's repositories, your tokens stop working for them at the same moment, without being revoked.

Publishing a website on each push

A files website in Websites can take its files from a repository in the same team. Each push to the branch it uses will publish the website again from the files at that commit, as they are or built from Markdown and templates.

Push your first project.

Create a Magpie account, open Git Repositories and create a repository, then copy its address into Git.

Create account