Let’s Git It
Let’s Git It is FOSS MEC’s beginner workshop on Git, GitHub and contributing to a real project. This library is the practice ground: every exercise uses the same repository that publishes this website.
What you will be able to do
By the end of the workshop you should be able to:
- explain the difference between Git and GitHub;
- fork a repository, create a branch and commit a change;
- open a pull request and respond to review;
- add a Markdown note or an external resource to this library;
- find the site’s source file from the Suggest an edit link.
You do not need to install anything. Everything can be done in a browser.
Before you arrive
- Create a free GitHub account and verify your email.
- Bring a laptop or a phone with a browser. A laptop is easier for file uploads.
- Read the contribution paths for two minutes.
- Optionally install Git locally if you want to practise the command line.
Workshop route
| Step | Time | What happens |
|---|---|---|
| 1. Concepts | 10 min | Repositories, commits, branches, forks, pull requests |
| 2. Tour | 10 min | The library structure and the browser-only GitHub editor |
| 3. Quickstart | 15 min | Fork → edit → commit → pull request |
| 4. Exercises | 25 min | Pick one task from the exercise list |
| 5. Review | 10 min | Read a partner’s PR and leave a kind, specific comment |
| 6. Merge and deploy | 5 min | A maintainer merges; GitHub Actions publishes the site |
Start here
15 minutes
Browser-only quickstart
Open your first pull request without installing Git.
Start the quickstart →
Practice
Workshop exercises
Seven non-conflicting tasks with acceptance criteria.
Choose an exercise →
Reference
Git cheat sheet
Commands, Markdown syntax and the PR checklist on one page.
Open the cheat sheet →
Ground rules
- One small change per pull request. Small PRs are reviewed faster and teach more.
- Do not edit
src/SUMMARY.mdunless you are adding a new chapter. Most fixes do not need it. - Only upload what you wrote or are allowed to share. State the licence in the PR.
- Be kind in review. Critique the change, not the person.
- Ask early. Open an issue or ask a maintainer if a step fails; do not guess around a permission error.
After the workshop
Continue with the Git Essentials guide and Collaborating on GitHub. Then pick a good first issue and keep contributing.