Git Tutorial for Beginners: Command-Line Fundamentals

Git command-line fundamentals hinge on one practical advantage: distributed version control keeps a full copy of repository history on every developer’s machine, so work can continue even when the central server is unreachable. In contrast to centralized systems like SVN—where access depends on a single server and outages or corruption can be catastrophic—Git’s distributed model means each local repository contains the information from the last sync. If the remote repository fails, developers still have the changes they pulled earlier, effectively acting as backups.

After that conceptual setup, the tutorial walks through getting Git installed and ready for real use. Installation comes from g-s cm.com, followed by a quick verification using git --version. The next step is global configuration: setting user.name and user.email with git config --global user.name "..." and git config --global user.email "..." so commits are attributed correctly across teams. To reduce friction later, built-in help is highlighted via git help <command> or git <command> --help, which opens the manual pages for commands like config and add.

From there, the workflow splits into two common scenarios: starting a new project locally and cloning an existing project from a remote source. For a local project, the process begins with git init inside the project directory, which creates a .git directory containing repository metadata. Running git status shows untracked files, and the tutorial emphasizes ignoring machine- or personal-specific files by creating a .gitignore file (including examples like *.pyc). Files move through three states: the working directory, the staging area, and committed history. git add stages changes—either selectively or with git add -A—while git reset can unstage them. A commit is created with git commit -m "message", and git log provides the commit hash, author, and message.

For remote collaboration, the tutorial uses git clone <url> <destination> to copy an existing repository into a local folder. It then demonstrates how to inspect remotes with git remote -v and list branches with git branch -a. When changes are made, git diff shows what changed, git add stages, git commit records locally, and git push sends updates to the remote. Before pushing, git pull is recommended to fetch any upstream changes from other developers; the example shows git pull reporting “already up to date” when nothing new exists.

Branching is presented as the standard way to develop features without disrupting master. The tutorial creates a branch with git branch <name>, switches with git checkout <name>, commits changes on that branch, and pushes it to the remote using git push -u origin <branch>. After tests pass, the feature branch is merged back into master via git checkout master, git pull, git merge <branch>, and git push origin master. Once merged, the branch can be deleted locally with git branch -d <branch> and remotely with git push origin --delete <branch>. The result is a repeatable daily routine: commit locally, sync with git pull, push with git push, and merge through branches when ready.