Git Repositories

Magpie hosts your team’s Git repositories. You clone and push with the Git tools you already use.

Git Repositories keeps your code in Personal or a team. You can read its files and commits on the page. Your team’s access settings decide who can push.

Create account
Callahan Studio’s private albers-coffee-site repository, with its folders and files, the last commit and its HTTPS clone address.

Git clones and pushes over HTTPS, with an access token as the password.

A token belongs to your account and works for every repository you can use. You choose whether it can read, push, or both. Magpie shows it once.

An empty repository shows the commands to start a project or push one you already have. The push brings its whole history. Anyone can clone a public repository without a token.

Callahan Studio’s new private paulina-bakery-menu repository, with its HTTPS clone address and the Git commands to start a project or push one you already have.

A repository’s page shows its files, its README and every commit.

The page lists the files on the default branch, with the last commit for each. Markdown files, the README among them, read as documents. Other text files show as text.

Commits lists the branch’s history, 30 to a page. A new repository can start with a README, a .gitignore and a license.

The history of Callahan Studio’s callahan-website repository: 14 commits on main, newest first, each with its message, author, date and short ID.

Your team’s access settings decide who can read a repository and who can push.

Team admins can read and push. Members can push when the team gives them edit access. With view access they can clone and pull. A guest from outside the team can be given Git Repositories and nothing else.

A repository starts private. A public one can be read and cloned by anyone, without signing in. Pushing to it still needs write access.

Callahan Studio’s Git Repositories, four private to the team and two public, then two repositories shared with Robin Mazur by Albers Coffee and Kettle & Crumb.

A push can publish your website.

Websites is Magpie’s area for building and hosting sites. A files website can take its files from a repository in the same team. Each push to the branch publishes the site again.

Questions

Can I move a repository I already have on another host?

Yes. You create an empty repository in Magpie and add it as a remote. A push sends your commits with their history. The empty repository’s page shows the commands, with its own address.

Can I take my code back out?

Yes. A git clone gives you the whole repository with its history, as with any Git host. Clones on your computers stay as they are if you delete the repository in Magpie.

Can someone outside my team work on a repository?

Yes. You can invite them as a guest of the team and give them Git Repositories. A guest takes no place on your plan. The Free plan has 10 guests; Pro and the Team plan have 100.

Who can see a private repository?

A private repository can be read by the team’s members and the guests given it. To anyone else, its address shows as not found.

Which plan do I need?

Git Repositories is on every plan. Making repositories, cloning and pushing are the same on each.

Create a Git repository.

Create a Magpie account, then make a repository in Personal or your team.

Get started free