How all of this connects to Git
Beginner Core Git
Why this matters
You now know the world Git lives in. This page closes the section by placing every concept on the Git map, so that when the next sections talk about commits and branches you already know what they are for. Keep it as a lookup table; it is also a table of contents for the rest of the course.
The map
| You learned about | In Git it is… | On GitLab / GitHub it is… | Taught in |
|---|---|---|---|
| Source code, plain text files | The files in the working tree | The Repository / Code view | Section 2, Section 4 |
| Project | A repository: the folder plus its .git history |
A project (GitLab) / a repository (GitHub) | Lesson 4.1 |
| Dependencies, manifests, lock files | Committed manifests, ignored installs (.gitignore) |
Dependency scanning, package registries | Lesson 4.3 |
| Build, artifact, runtime | Not stored in Git; produced by the pipeline from a commit | Pipeline jobs, artifacts, pinned images | Section 14 |
| Environments, deployments | A deployment is "this commit, running there"; branches and tags decide what deploys where | Environments, deployment jobs, protected environments | Lesson 14.6 |
| Configuration and secrets | Templates committed, real values ignored | CI/CD variables (GitLab) / Secrets (GitHub) | Section 8 |
| Logs | Not in Git | Job logs in the pipeline | Lesson 14.3 |
| Requirement, issue, ticket | The number in branch names and commit messages: #12 |
Issues, boards, milestones | Lesson 9.6, Lesson 10.6 |
| Feature, bug, hotfix, chore | Branch types: feature/, fix/, hotfix/, docs/ |
Labels on issues and merge requests | Section 6, Lesson 13.2 |
| Version, release | A tag on a commit | Releases with notes and artifacts | Lesson 13.6 |
| Rollback | Deploying an earlier commit or tag; sometimes git revert |
Redeploy from the environment page | Section 12, Lesson 14.6 |
| The workflow's private lane | A branch | Branches, protected branches | Section 6 |
| The workflow's "please merge this" | Nothing in Git itself | Merge request / pull request | Lesson 9.7, Lesson 10.7 |
| Review, approval | Nothing in Git itself | Comments, suggestions, approvals, CODEOWNERS | Lesson 13.7 |
| Roles | Nothing in Git itself | Members and roles, permissions | Lesson 9.3, Lesson 10.3 |
| Board columns | Branch exists → merge request open → merged | Boards, Projects | Lesson 1.9 |
| The terminal | Where git … runs |
Not applicable | Section 3, Section 5 |
| Markdown | Plain-text files Git can diff and merge | Rendered pages, issue and merge request text | Lesson 4.4 |
Notice the pattern in the third column: Git stores files and their history; GitLab and GitHub add everything that involves people and machines around that history: issues, merge requests, reviews, roles, pipelines. When someone asks "is that a Git thing or a GitLab thing?", this table answers.
A developer sentence, translated
"I branched off main for #21, pushed, opened an MR, CI is red because of lint, I'll fix it after standup and ask Dev for review; it should make the 1.2 release."
- branched off main for #21: created a branch from the main line to work on issue 21.
- pushed: uploaded the branch to the remote.
- opened an MR: asked, on GitLab, for it to be merged and reviewed.
- CI is red because of lint: the pipeline's Markdown or code style check failed.
- ask Dev for review: assign the maintainer as reviewer on the merge request.
- make the 1.2 release: be merged before the
v1.2.0tag is created.
By the end of Section 13 you will say sentences like this yourself.
What comes next
Section 2 builds the mental model of Git itself: the four areas, what a commit really is, and the names Git uses (HEAD, origin, main). Everything after that is practice.