Wrap-up and resources
Key Takeaways
- 1. Git from zero: snapshots of your work: Git saves full snapshots of your project with a message explaining each. Work on a branch and commit often in small steps.
- 2. GitHub: working with a team: Work on a branch, push it, open a pull request, ask for review, then merge. Every company follows this same rhythm.
- 3. Version Control: After your first commit and pull request: know what happens inside Git, fork repositories, name branches clearly, review others' work, and number releases with semantic versioning.
Glossary
| Term | Definition | Part |
|---|---|---|
| commit | A full snapshot of the project with a message and a unique id. | 1 |
| Staging area | Where you gather what goes into the next commit. | 1 |
| Branch | A movable pointer to a commit you work on apart from main. | 1 |
| origin | The default name of the remote you cloned from. | 2 |
| Pull request | A request to merge one branch into another, with review and checks. | 2 |
| Conflict | Two edits to the same lines needing a human decision. | 2 |
| Staging Area | An intermediate step in Git between editing a file and saving it as a permanent snapshot (commit). | 3 |
| HEAD | A pointer to the branch or commit you currently stand on. | 3 |
| Semantic Versioning | MAJOR.MINOR.PATCH numbering that signals the kind of change. | 3 |
Resources for this lesson
Grouped by type. Start with the official docs for precision, or an article or video for the explanation.
Official docs1
Done with this lesson?
Sign in to save your progress.