2.5. Reflection Checkpoint

Key Takeaways

• GitHub's three account tiers — personal, organization, Enterprise — nest rather than replace each other; repositories live under a personal account or an organization, never directly under Enterprise.
• The GitHub Flow keeps exactly one long-lived branch (main) always deployable; every change happens on a short-lived branch and merges back through a reviewed pull request.
• GitHub Flavored Markdown adds GitHub-specific extensions — task lists, autolinked issues, @mentions — on top of standard Markdown, and those extensions only work inside GitHub.
• GitHub Desktop handles local Git operations with a GUI; GitHub Mobile is for review and triage on the go, not for writing or committing code.

Connecting Forward

Phase 3 moves from workflow into the repository itself: the files every well-structured repo has, how repositories get created and organized, and what the Insights tab reveals about a project's health.

Self-Check Questions

• Why does "main is always deployable" matter more as a team gets larger, not less?
• If a repository is owned by an organization instead of a personal account, what changes about who can grant access to it?