Developer Tools
Learn Git & GitHub
Git records the history of your project so you can see what changed, when, and why, and go back if needed. GitHub hosts those repositories and adds collaboration tools such as pull requests.
Why teams use it
- It makes experimenting safe, because you can always return to a working state.
- Branches let several people work without overwriting each other.
- Pull requests give changes a place to be reviewed before they reach the main branch.
Where you will meet it
On any team, your work reaches production through a branch, a pull request, a review, and an automated pipeline.
What to learn, and in what order
Work through these roughly in order. Jumping to the advanced list before the basics are solid is the most common way people get stuck.
Beginner
- Why version control exists
- Repositories, commits and history
- Branches
- Pushing and pulling from a remote
Intermediate
- Merging versus rebasing
- Resolving conflicts
- Pull requests and code review
- Stashing, tagging and releases
Advanced
- History rewriting and when to avoid it
- Branching strategies for teams
- Automating checks with GitHub Actions
Have a project worth talking through?
Tell us what you're building or what's slowing your current system down. We'll give you a direct read on scope and approach.