Stage 6 · Lesson 8 of 8
Secrets, access and account safety
Protect your GitHub account as carefully as your email. Turn on , so a stolen password is not enough. Use SSH keys, or that only have the access they need.
Now and then, review which apps you have allowed into your account. Never commit passwords, API keys or .env files. GitHub's and catch some of these leaks, but not all.
If a secret leaks, first revoke it with the service that issued it, then clean the history if needed. Be careful with repositories and "job tests" from strangers that ask you to run install scripts; this is a known way to steal .
Common trapthinking a private repository makes committed secrets safe.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- BookFreePro Git
Scott Chacon and Ben Straub
Chapter 6 covers GitHub itself: forks, pull requests and maintaining a project
- GuideFreeContributing to a Project (GitHub Docs)
GitHub · Beginner
GitHub's own walkthrough of the fork, branch and pull request workflow
Practise
Keep handy
Also worth your time
A widely used commit message convention you will meet in many repositories
- roadmap.sh: Git and GitHubGo deeper
The GitHub half of the map: Actions, projects, security features and more