Key files
Files with fixed names tell GitHub how the project works
README, LICENSE, CONTRIBUTING, SECURITY and CODEOWNERS.
A good repository has a few files that GitHub knows by name. The read me is shown on the front page: it is the welcome. The license says what other people may do with the code. Three files are about the community. Contributing explains how to help. The code of conduct says how people should behave. Security says how to report a vulnerability in private. Code owners lists who must review changes to which paths. And git ignore lists what Git should not track.
Key files · Going deeper
What GitHub does with each file
They may live in the root, docs/ or .github/.
Creating repositories
Template, fork and clone copy different things
A template copies files only. A fork keeps history and a link. A clone is local.
There are three ways to make a copy of a repository, and the exam asks you to choose. Creating from a template copies the files, but not the history, and keeps no link to the original. It is for starting new projects from a pattern. A fork copies the files and the history, and stays linked, so you can propose changes back. A clone also has everything, but it lives on your machine. It is the copy you work in.
Creating repositories · Going deeper
Creating a repository, and its settings
Owner, name, visibility, README, .gitignore and licence.
Check yourself
Which way of starting a repository does this row describe?
Managing files
Every edit in the browser is still a commit
Editing on GitHub ends in a commit: straight to the branch, or to a new branch and pull request.
You do not need Git on your machine to change a file. On GitHub you can create, upload, edit or delete a file in the browser. When you save, GitHub asks for a commit message, and where the commit should go. Commit directly, and it lands on the branch at once. Or create a new branch and start a pull request, and the change is reviewed first. On a protected branch, only the second is allowed.
Managing files · Going deeper
File operations on GitHub
Blame, history, permalinks, and Git LFS for large files.
Insights
Insights describes a repository without its code
Pulse, Contributors, Traffic and the dependency graph.
The Insights tab holds the numbers about a repository. Pulse is a summary of recent activity: what was merged, what was closed. Contributors shows who has committed, and how much. Traffic shows how many people viewed and cloned the repository over the last fourteen days, and which sites sent them. And the dependency graph lists the packages this code relies on. Security alerts are built on that list.
Insights · Going deeper
Stars, watching and other signals
Stars bookmark, Watch notifies, feature preview shows betas.
Check yourself
Where in Insights are these numbers?
Upkeep
Archive what is finished. Delete what should not exist
An archived repository is read-only and can come back. A deleted one is gone.
Last, the life of a repository. An active repository does everything: people read it, push to it, and open issues and pull requests. When a project is finished, archive it. It becomes read only. Everyone can still read and clone it, but nothing can change. And you can unarchive it later. Deleting is different. The code, the issues and the wiki all go. So archive what is finished, and delete only what should not exist.
Upkeep · Going deeper · 1 of 2
Good upkeep
Description, topics, a current README, releases and tidy branches.
Upkeep · Going deeper · 2 of 2
Clue words for repositories
README, CODEOWNERS, template, fork, Traffic and archive.
Check yourself
What should the maintainer do with the repository?
Lesson complete
You finished “Working with repositories”
Answer the questions along the way to see your score here.