Git Repositories

Git repositories are owned by a Magpie team. A personal repository belongs to your Personal team. A shared repository belongs to the shared team you choose when you create it.

Repository access follows the team. A private repository can also be shared with an individual Magpie user without adding that person to the team. Public repositories can be read by anyone, but writing still requires repository or team write access.

Magpie stores the Git repository separately from the application files. Git remains the source of truth for commits, branches, tags, and files. Repository metadata, team access, and settings are managed in Magpie.

Use Git from a Mac

Magpie's command-line Git connection uses HTTPS. SSH keys are not used for this feature, so there is no SSH key to upload.

Open Get an HTTPS token from the Git Repositories page or a repository page. Give the token Git repository read access to clone or fetch, and Git repository write access to push. Select both permissions if you need to clone and push. The full token is shown once. Magpie cannot show it again.

If your account already has a Password Vault, Save in Password Vault opens it in a new tab with the token ready to save as an API credential. Unlock Password Vault and save the item. The token is transferred between the two tabs in the browser; it is not sent to Magpie again.

When the repository page provides its HTTPS URL, add it as a named remote. origin is only a conventional name; a repository can have several remotes.

git remote add magpie https://magpiemeetings.com/git/<repository-id>.git
git push -u magpie main

When Git asks for credentials, enter your Magpie username and use the access token as the password. Do not use your Magpie account password, and do not put the token in the URL. A macOS Git credential helper can store the token in Keychain.

An access token does not grant repository access by itself. The token's user must also have write access through the repository's team or as a repository collaborator. Revoking the token stops Git access that uses it.

To revoke a token, click Revoke in the token list and confirm. The list updates without leaving the page.

The HTTPS transport is being released in stages. If the repository page does not show an HTTPS URL and Git commands, command-line clone and push are not available for that repository yet.

Repository names must be unique within the current team. If the name is already in use, the create form identifies that repository name so you can choose another one.

Team editors can delete a repository from its page. Deletion removes it from Magpie and its Git URLs stop working.

When a repository has no commits, its page says that it is empty. When it has a README in .github, the repository root, or docs, Magpie renders that README below the file list using GitHub-Flavored Markdown.

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