Start here: a tour of a repository
This course is the second half of Git: working on GitHub with other people, from the terminal, and letting robots test and publish your work. It assumes you know commits, branches and push (the Git from zero to master course, modules 1 to 5).
| Module | What you learn |
|---|---|
| 1 | A repository's pages, README, issues and projects |
| 2 | Pull requests, reviews, merge methods and protected branches |
| 3 | The GitHub CLI (gh) |
| 4 | GitHub Actions: your first workflow |
| 5 | Continuous integration: tests on every push |
| 6 | Publishing and security: Pages, releases, secrets, permissions |
| 7 | Project: a full pipeline for a real app |
About 4 weeks at 3 to 4 hours a week.
The tabs of a repository
- Code: the files, the branches (the branch menu), the history (the clock icon), and the README shown below the files.
- Issues: the to-do list: bugs, ideas, questions.
- Pull requests: proposed changes waiting for review.
- Actions: the robots: tests, builds, deploys.
- Projects: boards to plan the work.
- Settings: visibility, collaborators, branch rules, Pages, secrets.
Press . (the dot key) on any repository and a full VS Code opens in the browser (github.dev). Press t to find a file by name, and y on a file to get a link that never changes, pinned to the current commit.
A good README
The README is the front page. It answers, in this order: what is this (one sentence and a screenshot), how to use it (install, run), how to help (link to CONTRIBUTING.md), and the license. GitHub writes it in Markdown:
# Study Tasks
Plan what you study, tick it off, see the minutes left.
## Run it
```bash
npm test
```
> [!TIP]
> Works offline: tasks stay in your browser.
| Feature | Status |
|---|---|
| Tasks | done |
| Sync | planned |