GitHub Collaboration (for SVN users)

The daily cycle: visualised

Step	Git	SVN equivalent
Get latest	`git pull`	`svn update`
Edit	(same)	(same)
Stage	`git add FILE`	(no equivalent)
Save locally	`git commit -m "msg"`	`svn commit`
Share	`git push`	`svn commit`

The fork triangle

git push origin → uploads to your fork
Pull Request on GitHub → proposes changes to upstream
git fetch upstream → downloads from the shared repo

## GitHub Issues

Issues are GitHub’s built-in bug tracker and task list.

**What they are for:**
- Reporting bugs (“X crashes when Y”)
- Requesting features (“It would be nice if…”)
- Tracking tasks and discussions

**Key features:**
- Markdown formatting (code blocks, math, links) — very similar to Zulip
- Labels for categorisation (bug, enhancement, question, …)
- Assign to people, link to PRs
- A PR can **close** an issue automatically: write `Fixes #42` in the PR description

All issues from Mantis have been synced here. From now on, new issues go on GitHub.

**Try it:** browse [github.com/Magma-Maths/core/issues](https://github.com/Magma-Maths/core/issues) to see real examples.

Notes:
- Issues are how you communicate about code without email.
- Show the Magma-Maths/core issues page live if time allows.
- The "Fixes #42" syntax is very useful — when the PR merges, the issue closes automatically.
- Labels and milestones help organise large projects, but don't need to explain those in detail now.