Git — The Akashic Repository

# Every file version is stored as a blob — raw content, nothing more
git cat-file -p a1b2c3d
# Output: the exact bytes of the file at that version
# The SHA is derived from the content itself — Chitragupta's seal

# A tree is a directory snapshot — blob refs + subtree refs
git cat-file -p HEAD^{tree}
# 100644 blob a1b2c3d  README.md
# 040000 tree e4f5a6b  src
# Every directory level is its own tree object

# A commit wraps a tree snapshot + metadata
git cat-file -p HEAD
# tree   e4f5a6b7c8d9e0f1
# parent a1b2c3d4e5f6a7b8   ← points to previous karma
# author Deveshwar Jaiswal
# committer Deveshwar Jaiswal
#
# feat: add authentication
# Each commit is a complete snapshot — never a diff

# HEAD is just a text file
cat .git/HEAD
# ref: refs/heads/main   ← attached (normal state)

# A branch is also just a text file — 41 bytes
cat .git/refs/heads/main
# a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0

# Detached HEAD — contains a SHA directly
cat .git/HEAD
# a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0   ← wandering soul

# Each commit is a karma — permanently sealed by Chitragupta
git add src/auth.ts
git commit -m "feat: add JWT validation"
# [main a1b2c3d] feat: add JWT validation
# SHA is deterministic — same tree + same parent + same message = same SHA

# A branch is a dharmic path — a parallel reality that costs nothing
git checkout -b feature/auth  # 41 bytes — that's the entire cost
git branch -v
# * feature/auth  a1b2c3d  feat: add JWT validation
#   main          a1b2c3d  feat: add JWT validation

# Fast-forward — paths that never diverged rejoin cleanly
git checkout main
git merge feature/auth
# Updating a1b2c3d..b2c3d4e
# Fast-forward — no merge commit, no karma clash

# 3-way merge — two dharmas converge, a new moment is born
git merge feature/auth
# Merge made by the 'ort' strategy.
# The merge commit has two parents — it carries both histories
git log --graph --oneline
# *   m7n8o9p Merge branch 'feature/auth'
# |\
# | * b2c3d4e feat: add JWT validation
# * | c3d4e5f fix: hotfix
# |/
# * a1b2c3d  init

# Maya — the perceived history rewrites, the actions are unchanged
git rebase main
# First, rewinding head to replay your work on top of it...
# Applying: feat: add JWT validation
# New SHA — same diff, new parent, new fingerprint
# The old commit is abandoned (no refs). Reflog preserves it.

# Selective karma — one action carried to another path
git cherry-pick a1b2c3d
# [main b2c3d4e] feat: fix critical bug
# Same diff, new SHA — a new moment with the same intention
# The source branch is untouched

# --soft: turn back the clock, keep your preparations
git reset --soft HEAD~1
# HEAD moves back. Changes stay staged. Ready to recommit.

# --mixed (default): return to before you staged
git reset HEAD~1
# HEAD moves back. Index cleared. Working tree unchanged.
# Your edits remain — just unstaged.

# --hard: pralaya — the dissolution
git reset --hard HEAD~1
# HEAD moves back. Index cleared. Working tree wiped.
# The commits still live in reflog for 90 days — nothing is truly lost.

# Samskara — latent impressions stored below the surface
git stash push -m "WIP: auth refactor"
# Working tree is clean. The impressions wait.
git stash pop
# The samskara surfaces — changes restored to working tree

# Multiple lokas — realms of the same codebase, existing simultaneously
git worktree add ../hotfix-dir hotfix/critical
# ../hotfix-dir is now checked out to hotfix/critical branch
# Both dirs share .git/objects — same Chitragupta keeps both ledgers
git worktree list
# /path/to/repo       a1b2c3d [main]
# /path/to/hotfix-dir b2c3d4e [hotfix/critical]