Check Change Files in Git

-

You can compare only the files that differ between your current local branch and another branch on the remote using Git. Here are the most common and useful ways, from simplest to more detailed.

1. List only the changed files (most common)

git fetch origin
git diff --name-only origin/other-branch

If you want to be explicit about your current branch:

git diff --name-only origin/other-branch..HEAD

➡️ Shows only file paths that are different.

2. List changed files with change type (added / modified / deleted)

git diff --name-status origin/other-branch..HEAD

Example output:

M src/app.js
A src/new-file.ts
D src/old-file.css

3. Compare against the common ancestor (recommended for PR-style comparison)

This avoids noise from changes made in the target branch after you branched.

git diff --name-only origin/other-branch...HEAD

... (three dots) means:
changes on your branch since it diverged from the other branch

This is usually what you want when preparing a PR.

4. Show actual diffs for only changed files

git diff origin/other-branch...HEAD

Or for a single file:

git diff origin/other-branch...HEAD -- path/to/file

5. If you want only committed changes (no working tree changes)

git diff --name-only origin/other-branch...HEAD

If you want to include uncommitted changes too:

git diff --name-only origin/other-branch...HEAD
git diff --name-only --cached

Quick cheat sheet

Goal Command
File list only git diff --name-only origin/branch...HEAD
File list + status git diff --name-status origin/branch...HEAD
Full diff git diff origin/branch...HEAD
Against exact branch state git diff origin/branch..HEAD
Total page views:

Comments

Post a Comment

Popular posts from this blog

Useful aliases

-
alias ll="ls -lah" alias branch="git branch" alias checkout="git checkout" commit() { echo "Enter commit message (Ctrl+D to finish):" msg=$(cat) git commit -m "$msg" } add() { # Ensure git repo git rev-parse --is-inside-work-tree >/dev/null 2>&1 || return 0 # Colors GREEN="\e[32m" RED="\e[31m" YELLOW="\e[33m" CYAN="\e[36m" BOLD="\e[1m" RESET="\e[0m" local current_branch remote_branch behind local files file answer local added_files=() local skipped_files=() local temp_ignored_files=() local existing_temp_ignored=() current_branch=$(git branch --show-current) # ---------- STEP 0: Check existing temp-ignore files ---------- mapfile -t existing_temp_ignored /dev/null 2>&1 || { echo -e "${RED}Fetch failed.${RESET}" return 1 } behind=$(git rev-list --count HEAD.."$remote_branch" ...
Read more

Start all Docker containers

-
To start (bring up) all existing Docker containers , use this: docker start $(docker ps -aq) Explanation docker ps -aq → lists all containers (running or stopped) docker start → starts stopped containers If you are using Docker Compose From the directory with docker-compose.yml: docker compose up -d Or for multiple compose projects (containers already created): docker compose start Useful checks See all containers and their status: docker ps -a See only running containers: docker ps Common gotcha If you see access forbidden , it means: Image not pulled (private registry) Not logged in Login first: docker login Then retry: docker start $(docker ps -aq)  
Read more