Git Repositories
Decide who can read and push to each Git repository.
A repository belongs to Personal or a team, and the team's members read it or push to it according to the team's Member access. A private repository is open only to the team; a public one can be read and cloned by anyone. Guests can be given Git Repositories without joining the team.
Get started freeTeam access
A repository belongs to the Personal or team selection that was open when it was created, and Git Repositories lists the repositories of the selected one. Who can do what follows the team's Member access setting, Can edit or View only.
- Admins
- Read and push to every repository in the team, create repositories, change their description and visibility, and delete them.
- Members, with Can edit
- The same as admins for the team's repositories.
- Members, with View only
- Read, clone and pull, but not push. They are not offered New Git Repository.
- Personal
- Repositories in Personal are yours, and open to the guests you give Git Repositories.
Private and public repositories
A new repository starts private: only the team's members can read it. To anyone else, a private repository's address shows as not found, the same as one that does not exist.
Members who can edit the team change the visibility from Edit details in the repository's More menu, and making it public asks for confirmation. Anyone can then read and clone it without signing in, at its public page and its clone address. Pushing still needs write access. Making it private again takes the public page down.
Guests
A guest is someone from outside the team who uses only the areas and records they were given. A guest takes no place on the plan and does not see the team's other pages. A team admin invites guests by handle or email address and chooses their areas.
- Everything in Git Repositories
- The guest uses the team's repositories as a member does, under the same Member access.
- How many guests
- 10 on the free plan and 100 on Pro and the Team plan.
Tokens follow the account
Git's tokens give no access by themselves: Git can read and push wherever the account can. When someone leaves the team or the team changes to View only, their tokens stop pushing to its repositories at the same moment, with nothing to revoke.
Deleting a repository
Members who can edit the team delete a repository from its More menu, after confirming. Magpie will stop serving it: its addresses will stop working for everyone and it will be removed from the team. A deleted repository does not go to Trash and cannot be restored from Magpie. Clones already on someone's computer are not affected.
Create a private repository for your team.
Create a Magpie account, select your team and choose New Git Repository in Git Repositories.