GitHub Repositories
📌 Covered in this chapter:
Public vs Private Repos · README · .gitignore · License · Repository Settings
Create and configure a repository on GitHub — public vs private, README, .gitignore, and license basics.
1GitHub Repositories — What You'll Learn
Create and configure a repository on GitHub — public vs private, README, .gitignore, and license basics.
Here's everything this chapter covers, in the order you'll learn it:
- Creating a GitHub account
- What a repository is on GitHub
- Public repositories (visible to everyone)
- Private repositories (restricted access)
- Choosing a repository name
- Writing a description
- Adding a README
- Adding a .gitignore template
- Choosing a license
- Setting the default branch
- Repository settings overview
- Repository visibility changes
2Best Practices & Common Pitfalls
💡 Key things to remember:
- Add a README and .gitignore right when you create the repository on GitHub — it saves you from manually creating them locally afterward.
- Public repositories are visible to anyone, including search engines — never put secrets or credentials in a public repo.
❓ Frequently Asked Questions (FAQ)
Q What's the most important thing to understand about github repositories?
Focus on: Public vs Private Repos · README · .gitignore · License · Repository Settings. These are the core building blocks this chapter's examples are built around, and they show up repeatedly in later chapters of this course.
Q Is github repositories something I'll use often in real projects?
Yes — every concept in this chapter reflects a real, everyday part of professional Git and GitHub workflows, not just a theoretical exercise.