repository
Also called: repo
A project folder together with its complete history of changes. On GitHub it has its own page with files, commits, branches and pull requests.
A repository (repo for short) holds two things: the current files and every commit that led to them. On GitHub the repository page shows the file tree of the selected branch, the latest commit, the number of commits and branches, and the README below the files. Tabs across the top (Code, Issues, Pull requests, Actions, Projects) open the team's work around the code.
Example
catchow/website is the repository of the CatChow online shop: page templates, prices in a config file, texts and images.
Learn it in the course
- Why teams keep history: version control without fear · What version control is, how Git differs from GitHub, and why looking around a repository can't break anything.
- Repository and commits: reading a repo page · A GitHub repository page from top to bottom, what a single commit page tells you, and what makes a good commit message.
- Reading history: messages, diffs and blame · How to open a file's history, read a diff line by line and use blame to trace any line back to its commit, pull request and issue.