Session 0 — Exercises: First Repository and GitHub Tour
Last updated on 2026-04-17 | Edit this page
Overview
In this session you will create your first repository on GitHub, write a short README, and explore the GitHub interface.
Time frame: approximately 60 minutes of hands-on work.
Task 1: Create Your First Repository
Step 1 — Create a new repository on GitHub
- Go to github.com and sign in.
- Click the + button in the top-right corner and select New repository.
- Name your repository
git-intro-<yourname>(replace<yourname>with your actual name or username). - Check Add a README file.
- Click Create repository.
Checkpoint 1
You should now see your new repository page with a
README.md file displayed.
Step 2 — Alter content of your README
Click the pencil icon (✏️) on the
README.mdfile to edit it.-
Add a heading with your name and 2–3 bullet points about yourself, for example:
Scroll down, write a short commit message (e.g. “Add personal info to README”), and click Commit changes.
Checkpoint 2
Your README now shows your name and personal information. You should see 2 commits in the repository history.
Step 3 — Explore Markdown formatting
Enhance your README with additional Markdown features:
- Add a link to this course material.
- Add a numbered list of your top 3 goals for this workshop.
- Try using bold and italic text.
Task 2: Explore the GitHub Interface
Level 1 — Navigate the repository page
Explore the following areas of your repository and note what you find:
- Code tab — Where are your files listed?
- Commits — Click on the commit count to see your commit history.
- Settings — Find where you can change the repository name or visibility.
Task
Change the visibility of your project to “private” (if it is currently public) or to “public” (if it is currently private).
To do this:
- go to “Settings”
- find the respective option in the “General” section
- change the visibility and confirm the change by typing the repository name when prompted.
Checkpoint 3
You can navigate to the commit history and identify who made each commit and when.
Level 2 — Discover more GitHub features
Explore these additional features:
- Issues tab — Open a new issue titled “Test issue” with a short description. Close it afterwards.
- Pull requests tab — Note that it is empty for now (we will use it later).
Task
Open a new issue by spotting a “typo” in your README and describing how to fix it. To this end:
- go to “Code”
- click on your
README.mdfile (to show its content) - switch from “Preview” to “Code” to see the raw markdown
- select on of the markdown lines (should be highlighted in yellow)
- this should trigger the popup of a
...menu, where you can select “Reference in new issue” to create a new issue with the selected line as content. - add a title and description to the issue, and submit it.
Level 3 — Repository settings deep dive
- Disable “Wiki” and “Projects” features in the Features section of the General Settings.
- Find the Danger Zone in Settings. What other options are available there?
- Settings — Find where you would add a collaborator.
Task
You should add your course supervisor as a collaborator to your repository, so that they can see it and provide feedback.
To do this:
- go to “Settings”
- click on “Collaborators” in the left sidebar
- add the GitHub user name of your course supervisor and click “Add
collaborator”
- choose “write” permissions for the collaborator, so that they can also edit the repository if needed.
The course supervisor will receive an email invitation to collaborate on your repository, which they need to accept before they can see it.
Checkpoint 4
You can navigate the GitHub page, identify where to find commits, issues, and settings, and understand the different features available in the repository settings.
Task to complete before next session:
Either add the course supervisor as a collaborator to your repository, or make sure your repository is public so that we can see it.
Summary
By the end of this session you should have: