A Tour of a GitHub Repository
What every tab does.
A repository page on GitHub has a lot going on. Every tab maps to something you already know from Git. Let's take a tour, so nothing feels unfamiliar.

- A busy page
- Every tab maps to Git
- A quick tour
The tabs
The code tab shows your files, and the readme below them. Issues is the to do list. Pull requests lists open and merged pull requests. Actions shows your workflow runs. And settings holds things like collaborators, branch protection, and Pages.
| Tab | What it shows |
|---|---|
| Code | files, README, branches |
| Issues | bugs and ideas |
| Pull requests | proposed changes |
| Actions | workflow runs |
| Settings | access, rules, Pages |
Inside the code tab
Inside the code tab, there's more. The branch menu switches between branches, just like git switch. The commits link is the same as git log. Every file has a history button, like git log with a file name, and a blame button, like git blame. And the green code button gives you the address for git clone.
| key | value |
|---|---|
| Branch menu | like git switch |
| Commits | like git log |
| History / Blame | per file |
| Green Code button | URL for git clone |
Summary
Code, issues, pull requests, actions and settings. Each one is a window onto the Git you already know. Next, inviting people to your repository.
Key takeaways- Code: files and history
- Issues and PRs
- Settings: access and rules