Git Pull

git pull fetches commits from a remote repository and merges them into your current local branch. It’s actually two commands in one — git fetch followed by a merge (or rebase, depending on configuration) — which is exactly why modern Git insists you tell it which reconciliation strategy you want. This is the tenth post in this site’s Git command guide, following Git Push.

Continue reading Git Pull

Git Log

git log displays the commit history of a repository — author, date, commit hash, and message, in reverse chronological order with the most recent commit first. It’s the command I reach for whenever I need to answer “who changed this and when,” and it has far more useful flags than the bare command suggests. This is the eleventh post in this site’s Git command guide, following Git Pull.

Continue reading Git Log

Git Status

git status shows you the current state of your working directory and staging area — which files are tracked, which have been modified, which are staged for the next commit, and which Git doesn’t know about at all. It’s the command I run more than any other Git command, usually right before deciding what to do next. This is the sixth post in this site’s Git command guide, following Git Commit.

Continue reading Git Status

Git Add

git add is the command that stages changes from your working directory into Git’s index, marking them to be included in the next commit. Staging is an intermediate step that gives you precise control — you can add one file at a time, leaving other modified files unstaged until a later commit. This is the third post in this site’s Git command guide, following Git Clone.

Continue reading Git Add