⚙️ Installation and First Configuration

Installation and First Configuration: Installing Git is like registering as an official contractor before stepping onto a building site: the gate logs your badge number, your nam

Installing Git is like registering as an official contractor before stepping onto a building site: the gate logs your badge number, your name, and which door you entered — every nail you hammer is traceable to you. The question to sit with before moving to commands is: why does Git need your name and email at all, given that you are the only one at your keyboard right now? Because six months later, when the CI pipeline breaks on a specific commit, "who changed this?" is the first question the team asks — and without proper author metadata, you are all anonymous. Java analogy: in Maven or Gradle you declare coordinates — groupId, artifactId, version — before the project can be published anywhere; `git config --global user.name` is the same declaration layer for your commits. In QA, wrong or missing identity in commits means audit logs are useless, CODEOWNERS triggers cannot auto-assign reviewers, and GDPR-relevant code change traceability breaks.

Before Git commands: understand the terminal tools

git-terminal-shell-map

Terminal, Shell and Git: who does what?

Watch one command travel from the visual terminal window to the shell engine, then to Git and back as readable output.

git-terminal-install-use

Download, install, open, verify: the safe first run

Follow the beginner path for Windows Git Bash, macOS Terminal, Linux terminal and IDE terminals before touching a real project.

Try It Yourself: First safe terminal tour

Inside Git Bash or a terminal, first see where you are, create a folder, enter it, verify Git, and ask for repository state.

See which folder you are in first

List what is in the current folder

Create a practice folder

Enter the new folder