Git Repositories

Git Repositories holds Git repositories for Personal or a team. A repository belongs to the Personal or team selection that was open when it was created, and Git Repositories lists the repositories in the current selection. Repositories in other teams that were shared with you directly are listed under Shared with you, with their team's name.

To clone a repository or push to it from your computer, see Clone and push with a token or SSH key.

Create a Git repository

Choose New Git Repository and enter a name: letters, numbers, dots, hyphens and underscores, starting with a letter or a number. The name must not already be used in the same team, and it cannot be changed later.

Under Starter files you can add a README, a .gitignore and a license. The license names the team as the copyright holder. Anything chosen there is the repository's first commit, so you can clone it straight away. Without starter files the repository is empty until someone pushes to it.

A new repository starts private and opens next. You need edit access to the team to create a repository in it; members who cannot edit the team are not offered New Git Repository.

Files and commits

A repository's page shows its team, whether it is public or private, its default branch and its description. Files lists the files on the default branch, folders first, with each file's size and the date, subject and author of the last commit. Open a file to read it: Markdown files, including the README, are shown as a document, other text files as text. Open a folder to list up to 200 of its items. Binary files and files over 1 MB are not shown. The page lists the README with the other files; open it to read it.

Commits lists every commit on the default branch, newest first, 30 to a page. Below the files, the page shows the address to clone the repository.

A repository nothing has been pushed to yet shows the clone address first, with the commands to start a project on your computer or to push one you already have.

The page shows only the default branch. The name and default branch cannot be changed.

Description and visibility

Members who can edit the team choose More, then Edit details…, to change the description or the visibility. The description is shown under the name and on the public page, and can use Markdown. Each change is saved as soon as you make it. Making a repository public asks you to confirm first.

• Private: only the team's members and people it was shared with can read it.
• Public: anyone can read and clone it without signing in. Pushing still needs write access.

Public repository page

A public repository has a public page at /g/<team>/<repository>, its clone address without .git. Open public page on the repository's page opens it. It shows the name, description and default branch, a line with the last commit's message, author and date, the number of commits, the files with their sizes, and the HTTPS clone address with Copy.

The number of commits opens the history at /g/<team>/<repository>/commits: each commit's message, author, date and short ID, newest first, 30 to a page. Select a folder to list up to 200 of its items, folders whose names start with a dot included, or a file to read it. Markdown files are shown as a document, other text files as text. Each folder and file has its own address under /g/<team>/<repository>/files/, so it can be shared. The names above a folder or file lead back up to the repository. Open as plain text beside a file's name shows the file as plain text, never as a web page, so an HTML or SVG file shows its source. Binary files and files over 1 MB are not shown. Signed-in people who can open the repository in Magpie see Open in Magpie.

Making a repository private takes its public page down.

Who can read and push

Access follows the team that owns the repository and its Member access setting (see Create and manage a team). Team admins, and members when the team gives members edit access, can read and push. When the team gives members view access, they can read and clone but cannot push.

A repository can also be shared with one person, with read-only or read-and-write access. This is done in the Magpie app: open the repository, choose Collaborators from its menu, and enter the person's handle. Someone who is not on the team will be invited, and can read the repository once they accept, as a guest of the team; see Guests on a team. Until then the screen lists them under Invited, with Cancel. A guest of the team is added at once, and members of the team already have access.

The same screen changes a person's access or removes it. Removing someone who has nothing else in the team also removes them from it, and the confirmation says so. A person given a repository this way sees it in Git Repositories when its team is selected, and under Shared with you otherwise.

On the website, a private repository you cannot read shows as not found, the same as one that does not exist. A repository missing from Git Repositories may belong to another team: select that team to list it.

Publish a website from a repository

A files website in Websites can take its files from a repository in the same team, so each push publishes them. See Build a website from a Git repository.

Delete a repository

Members who can edit the team choose More, then Delete repository, and confirm. Magpie stops serving the repository: its addresses stop working for everyone and it is removed from the team. It does not go to Trash and cannot be restored from Magpie. Clones already on someone's computer are not affected.

In the Magpie app

In the native app, Git repositories lists the repositories in the selected Personal or team, and Shared with you lists those shared with you from other teams. Search covers every team, and you can filter by visibility. Opening a repository shows its owning team, visibility, default branch and clone address. You can choose a branch, open folders, read text files and see recent commits. The app shows up to 200 items in a folder, the latest 25 commits, and text files up to 128 KB.

Tap New to create a repository in the current selection. In the app you can also enter a description and choose public or private when you create it, along with the same starter files as the website.

Members who can edit the team can open Settings from a repository's menu to change its description or visibility, Collaborators to share it, and Delete repository to delete it. To create and revoke HTTPS tokens in the app, see Clone and push with a token or SSH key. SSH keys cannot be added in the app.

For access or repository state that does not match the page, Contact support.