What is the difference between GitHub and Magpie?
GitHub is a platform for writing, reviewing, testing and shipping code. It has issues, project boards and Pages beside it. Magpie is one subscription for a small business's software. Its Git Repositories and Issues are two areas beside Websites, Time Tracking, Invoicing and the rest. GitHub does more with the code itself; Magpie does more around it.
Does Magpie replace GitHub?
Yes, for a small team that pushes to private repositories and tracks work as issues. Magpie hosts the repositories, plans the work and publishes a website on each push.
Consider keeping GitHub if you review changes in pull requests or run tests on every push. Keep it if you need security alerts. Keep it too if outside contributors send changes through forks. GitHub does each of these better than Magpie does today.
How much does GitHub cost?
GitHub has a Free plan and paid plans priced per user: Pro for one person, Team and Enterprise for organizations. Free includes unlimited public and private repositories and 2,000 Actions minutes a month. Copilot, Secret Protection and Code Security are priced on their own. The prices are on GitHub's pricing page.
How much does Magpie cost?
Magpie has a Free plan and paid plans, each covering every area. Git Repositories and Issues are on every plan. A free team has places for 3 people. The Team plan has places for 25, at one price for the team. The prices are on Magpie's pricing page.
Does Magpie have pull requests?
No. Members merge with Git on their computer and push the result. Nothing in Magpie reviews a change or requires an approval before a merge. Pull requests are on Magpie's roadmap. GitHub's pull requests hold the change, its discussion and its reviews.
Can I see what a commit changed in Magpie?
No. Commits lists each commit's message, author, date and short ID, without the lines it changed. People read the changes with Git on their computer. GitHub shows every changed line of a commit or a comparison.
Does Magpie show branches other than the main one?
No, not on the website. Git pushes any branch to a Magpie repository, but its page shows only the default branch. The Magpie app can choose a branch to read. It is not yet in the App Store or Google Play. GitHub lets you choose any branch.
Does Magpie run tests or builds on each push?
No. A push to a repository can rebuild a website made from it, and nothing else runs. Build jobs are on Magpie's roadmap. GitHub Actions runs build, test and deploy workflows, with 2,000 minutes a month on Free.
Can I edit a file on Magpie's website?
No. Files are read-only on the website, and changes arrive by pushing with Git. GitHub edits a file in the browser and commits it.
Does Magpie check my code for security problems?
No. Magpie does not read a repository's dependencies, check pushes for keys or scan the code. GitHub's Dependabot warns about vulnerable libraries, and secret scanning is free on public repositories.
Does Magpie support Git LFS?
No. A Magpie repository holds only what ordinary Git pushes. GitHub's Git Large File Storage keeps files of up to 2 GB each on Free and Pro.
Does GitHub have time tracking or invoicing?
No. GitHub's issues carry assignees, labels, types and milestones, and nothing records the time spent. In Magpie, Start timer on an issue records time in Time Tracking. That time can go on an invoice.
Can customers report a bug without an account?
In Magpie, yes. A public issue form takes a title, a description and an optional email address from anyone. Each report becomes an issue and waits in Triage. GitHub's help says opening an issue needs at least the Read role on the repository.
Does Magpie have an AI that writes code?
No. The assistant reads a repository's branches, recent commits, file tree, README and a file you name. It answers questions about them, and does not write code, commit or review changes. GitHub Copilot completes code, opens pull requests for an issue and reviews changes.
Can I publish a website from a repository on Magpie?
Yes. A files website takes its files from a repository in the team. Each push makes the site again. Markdown pages with Twig layouts are built; anything else is published as it is. A Jekyll or Hugo site is built on your computer first. GitHub Pages builds Jekyll itself and other generators through Actions.
Can I use GitHub and Magpie together?
Yes. An Issues project can be linked to a GitHub repository. Its issues then list the GitHub pull requests and commits you add. People can sign in to Magpie with a GitHub account. A team can keep code review on GitHub and plan, bill and publish in Magpie.
How do I move a repository from GitHub to Magpie?
Create a repository in Git Repositories without starter files and copy its clone address. In your clone, add that address as a remote. Push every branch and tag to it. Over HTTPS, Git asks for a password: paste a Magpie token. Over SSH, add your key in Magpie first. Pull requests, wikis and releases stay on GitHub.
Can I bring my GitHub issues into Magpie?
Yes. Save a repository's issues as JSON with GitHub CLI. Upload the file on Import issues, up to 200 issues at a time. The import keeps the number, title, body, labels, first assignee and dates. Comments, attachments and pull requests are not imported.
Does Magpie have a phone app?
Git Repositories and Issues work in a phone's browser, the issue board included. The Magpie app has them too. It is not yet in the App Store or Google Play. GitHub Mobile reviews and merges pull requests and brings notifications.
What is included in Magpie's Free plan?
Git Repositories, Issues, 1 website, Time Tracking, Invoicing, Store, Meetings, Forms and a team of 3. A paid plan raises the limits and adds email at your domain.