Linking Answers to Your GitHub Code
45 min · Intermediate
Your GitHub repository is the evidence behind every project answer. A clear README, a readable commit history and a working link let an interviewer check your story in a minute, and let you point at real code while you talk.
Topics in this lesson
- A README that sells the project
- Clean commit history and meaningful messages
- Pinning projects and keeping the resume link working
- Navigating your repository live during an interview
Interview questions this lesson answers
- What is a README file?
- What is the difference between Git and GitHub?
- What is a commit?
- What should a good README contain?
- Can you show me your GitHub?
- What makes a good commit message?
- Why does your repository have only one commit?
- How do you keep passwords and keys out of GitHub?
- Walk me through the code that places an order, on screen.
- What should never be committed to a public repository?
Sign in free to continue this lesson
Create a free account to read every lesson, practise with the exercises and keep track of your progress.