Created by Gagan Sir

GitHub Complete Master Manual

Complete Comprehensive Reference covering all 64 Topics & 25 PDF Pages

Created by Gagan Sir
Module 01: Git & GitHub Foundations, Installation & Repository Setup
Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
1
Git and GitHub Fundamentals & Mental Model
🇬🇧 English Definition
Git is a distributed version-control system that tracks local file changes, commits, and branch history. GitHub is a cloud hosting platform for Git repositories that adds collaboration tools like Pull Requests, Code Review, Issues, Actions CI/CD, and Security scanning.
🇮🇳 Hinglish Definition
Git tumhare local machine par code changes aur history ko track karta hai. GitHub isi code ko online host karke team collaboration, review aur automation provide karta hai.
🔄 Mental Model Architecture Flowchart
Working Tree
Edited files
➔
Staging Area
Staged changes
➔
Local Git Repo
Committed snapshots
➔
GitHub Remote
Cloud repository
TermMeaningExample
RepositoryProject + Git history database.git directory + project files
Working treeFiles currently being editedapp.py modified
Staging areaNext commit selection buffergit add app.py
CommitRecorded snapshot in historyabc1234 SHA hash
BranchMovable commit pointer referencemain, feature/login
RemoteNamed external GitHub repositoryorigin
Pull requestProposed change for peer reviewfeature/login ➔ main
WorkflowGitHub Actions CI/CD automation.github/workflows/ci.yml
2
Install Git and GitHub CLI
// Verify Git installation git --version git --help // Verify GitHub CLI installation gh --version // Authenticate GitHub CLI with browser/token gh auth login gh auth status
ToolPurpose / Description
GitCore version control engine
Git BashUnix-like terminal shell on Windows
PowerShellWindows terminal automation shell
GitHub CLI (gh)GitHub interaction directly from terminal
VS Code / IDECode editing, Git integration and visual diff debugging
3
First-Time Git Configuration
git config --global user.name "Your Name" git config --global user.email "you@example.com" git config --global init.defaultBranch main // Inspect active configuration git config --global --list git config --list --show-origin // Recommended optional settings git config --global core.autocrlf true git config --global fetch.prune true git config --global pull.rebase false
4
Authentication: HTTPS, SSH and Tokens
MethodUse CaseKey Security Idea
HTTPSClone/push over HTTPSRequires Personal Access Token or Credential Helper
SSHClone/push with key pairPrivate key stays safe on your machine
Token (PAT)API / HTTPS authenticationTreat like password; scope narrowly
GitHub CLI authTerminal authentication`gh auth login` automates secure token exchange
// SSH Key Generation (ed25519) ssh-keygen -t ed25519 -C "you@example.com" // Add ~/.ssh/id_ed25519.pub to GitHub Account Settings -> SSH Keys // Test SSH Connection ssh -T git@github.com
5
Create / Clone a Repository
// Clone existing remote repo git clone git@github.com:USERNAME/REPO.git cd REPO git remote -v git status // Initialize local repo and connect to GitHub remote mkdir my-project cd my-project git init git branch -M main git remote add origin git@github.com:USERNAME/my-project.git
6
Repository Structure & Important Configuration Files
Path / FilePurpose & Best Practice
.git/Git metadata and internal object database
README.mdProject overview, setup guidelines & usage documentation
.gitignoreExcludes build artifacts, secrets, and node_modules from Git
LICENSELegal open-source or proprietary licensing terms
CONTRIBUTING.mdGuidelines for external open-source contributors
SECURITY.mdVulnerability reporting instructions & contact details
CODEOWNERSDefines path-based review ownership rules
.github/workflows/GitHub Actions CI/CD automation workflow YAML files
.github/ISSUE_TEMPLATE/Standardized issue submission forms
.github/PULL_REQUEST_TEMPLATE.mdStandardized PR submission checklist
.github/dependabot.ymlAutomated dependency update configuration
CHANGELOG.mdHuman-readable version release history
Created by Gagan Sir
Module 02: Git Core Lifecycle, Branching, Merging & Rebase
Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
7
Git File Lifecycle
🇬🇧 English Definition
Git moves changes through 4 main states: Untracked/Modified, Staged (index buffer), Committed (local repository snapshot), and Pushed (GitHub remote repository).
🇮🇳 Hinglish Definition
File pehle working tree mein change hoti hai, phir `git add` se staging area mein jaati hai, `commit` se local history mein aur `push` se GitHub par.
🔄 File Lifecycle Flowchart
Untracked / Modified
Working Tree
➔
Staged
Index Buffer
➔
Committed
Local History
➔
Pushed to GitHub
Remote Repo
8
Essential Git Command Reference Table
CommandSyntax ExamplePurpose
initgit initCreate new local repository
clonegit clone URLCopy remote repository
statusgit statusInspect current repository state
addgit add .Stage modified files
commitgit commit -m "msg"Create permanent commit snapshot
loggit log --oneline --graphView commit history graph
showgit show SHAInspect specific commit details
diffgit diffInspect unstaged differences
switchgit switch -c branchCreate and switch branch
branchgit branch -aList local and remote branches
mergegit merge branchCombine history of branches
rebasegit rebase origin/mainReplay commits on new base
fetchgit fetch originDownload remote references
pullgit pullFetch + integrate remote changes
pushgit push -u origin branchUpload local commits to remote
restoregit restore fileDiscard uncommitted local changes
resetgit reset --soft HEAD~1Move branch pointer backwards
revertgit revert SHACreate inverse commit safely
stashgit stash push -m "WIP"Temporarily shelve changes
taggit tag -a v1.0.0 -m "msg"Create annotated version tag
remotegit remote -vDisplay configured remote URLs
cleangit clean -nPreview untracked files cleanup
refloggit reflogInspect reference log for recovery
9
git status / diff / add / commit Workflow
git status git diff git add . git diff --cached git commit -m "feat: add user registration" // Stage specific file git add app.py // Stage selected interactive chunks (patch mode) git add -p
🔍 Recommended Habit
  • status ➔ diff ➔ stage ➔ diff --cached ➔ commit. This prevents accidental secret files from entering history.
  • 10
    Commit Messages & Conventional Commits
    TypeExampleUse Case
    featfeat: add payment APINew feature for end user
    fixfix: handle null user inputBug fix
    docsdocs: update setup guideDocumentation only
    refactorrefactor: simplify auth middlewareCode change without behavior alteration
    testtest: add login integration testAdding or modifying tests
    chorechore: update dependenciesMaintenance task
    buildbuild: update Docker toolchainBuild system / external dependencies
    cici: add GitHub Actions matrixCI/CD workflow changes
    git log --oneline --graph --decorate --all git show HEAD git show HEAD~1 git log --since="2 weeks ago" git log --author="Name" git log -- path/to/file.py
    11
    Branches and Naming Conventions
    git branch git branch -a git switch -c feature/login git switch main git branch -m feature/login feature/user-login git branch -d feature/user-login // Push new branch to remote git push -u origin feature/user-login git push origin --delete feature/user-login
    12
    Merge and Fast-Forward
    git switch main git pull --ff-only git merge feature/user-login // Abort conflicted merge git merge --abort
    🇬🇧 Fast-Forward Merge
    Fast-forward occurs when the target branch HEAD has no divergent commits; Git moves the main pointer forward directly without creating an explicit merge commit.
    🇮🇳 Non-Fast-Forward Merge
    Jab dono branches par alag-alag commits ban jaate hain, toh Git divergent histories ko merge commit ke through combine karta hai.
    13
    Merge Conflicts Resolution
    git status git diff // Resolution Steps: // 1. Manually edit file to remove conflict markers and select clean code // 2. Stage resolved file: git add app.py git commit -m "fix: resolve merge conflict in app.py" // Cancel merge if needed: git merge --abort
    14
    Rebase and Interactive Rebase
    git fetch origin git switch feature/login git rebase origin/main // Interactive Rebase (Clean last 5 commits) git rebase -i HEAD~5
    ActionMeaning
    pickKeep commit in history as is
    rewordKeep commit but edit commit message
    editPause rebase to modify commit content
    squashCombine commit into previous commit
    fixupCombine commit into previous commit and discard message
    dropRemove commit completely from history
    🎯 Golden Rule of Rebase
    Never rebase commits that have already been pushed to a shared/protected public branch. Use rebase strictly for cleaning up private local feature branches before merging.
    Created by Gagan Sir
    Module 03: History Recovery, Remotes, Advanced Tools & Storage
    Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
    15
    Restore vs Reset vs Revert
    GoalCommandBest Use Case & Safety
    Discard file changesgit restore fileUnstaged local changes
    Unstage filegit restore --staged fileRemove file from staging index
    Undo shared commitgit revert SHASafe for team/remote history
    Move HEAD, keep changesgit reset --soft HEAD~1Local history cleanup
    Move HEAD and indexgit reset HEAD~1Local history cleanup
    Discard local changesgit reset --hard HEAD~1Dangerous; rewrites history permanently
    git restore app.py git restore --staged app.py git revert abc1234 git reset --soft HEAD~1 git reset HEAD~1 git reset --hard HEAD~1
    16
    Reflog and Recovery
    🇬🇧 English Definition
    Git reflog (reference log) records every movement of HEAD and local branch pointers. It allows recovering lost commits, deleted branches, or aborted rebases.
    🇮🇳 Hinglish Definition
    Reflog Git ke sabhi local pointer movements ka record rakhta hai. Galti se reset ya branch delete hone par reflog se exact SHA dhoondh kar recover kar sakte hain.
    git reflog git reflog show main // Recover lost commit by creating a new branch at lost SHA git switch -c recovery_branch abc1234 git show abc1234
    17
    Git Stash
    git stash push -m "WIP login form" git stash list git stash show -p stash@{0} git stash apply stash@{0} git stash pop git stash drop stash@{0} git stash clear
    18
    Remote Repositories: fetch / pull / push
    git remote -v git remote show origin git fetch origin git fetch --prune origin git pull git pull --rebase git pull --ff-only git push -u origin feature/login git push --force-with-lease
    19
    Tags and Releases
    git tag git tag -a v1.0.0 -m "Release version 1.0.0" git show v1.0.0 git push origin v1.0.0 git push origin --tags // Delete tag git tag -d v1.0.0 git push origin --delete v1.0.0
    20
    Advanced Git Tools (Cherry-pick, Bisect, Worktree, Rerere)
    CommandPurposeTypical Use Case
    git cherry-pickApply specific commit to current branchBackport hotfix from main to release branch
    git bisectBinary search commit historyFind exact commit that introduced a bug regression
    git worktreeMultiple working directories attached to single repoWork on feature and hotfix concurrently
    git rerereReuse recorded resolution of conflicted mergesRepeated conflict resolution during rebases
    git range-diffCompare two commit seriesReview interactive rebase changes
    // Cherry pick git cherry-pick abc1234 // Bisect binary search git bisect start git bisect bad git bisect good v1.0.0 // test project git bisect good // or git bisect bad git bisect reset // Worktree git worktree add ../hotfix hotfix/payment git worktree list git worktree remove ../hotfix
    21
    Submodules and Git LFS
    // Add Git Submodule git submodule add https://github.com/org/shared-lib.git libs/shared-lib git submodule update --init --recursive // Configure Git Large File Storage (LFS) git lfs install git lfs track "*.psd" git add .gitattributes design.psd git commit -m "chore: track design asset with LFS"
    Created by Gagan Sir
    Module 04: GitHub Workflow, Issues, PRs, Code Review & Rules
    Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
    22 & 23
    GitHub UI & Issues / Project Planning
    🇬🇧 English Definition
    GitHub Issues track bugs, tasks, and feature requests. GitHub Projects provides kanban boards, tables, and roadmaps to organize, prioritize, and monitor work progress.
    🇮🇳 Hinglish Definition
    Issue mein bug, task ya feature proposal record hota hai. Projects board aur roadmap ke through puri team ke tasks ko visually arrange karta hai.
    📋 Typical Software Engineering Lifecycle
  • Issue ➔ Feature Branch ➔ Commits ➔ Pull Request ➔ CI Checks & Review ➔ Merge ➔ Production Release.
  • 24
    Pull Requests (PRs)
    git switch -c feature/profile // make changes & test git add . git commit -m "feat: add profile endpoint" git push -u origin feature/profile // Open GitHub PR: base: main <- compare: feature/profile
    PR Template SectionWhat to Write
    TitleClear summary of business outcome
    DescriptionWhat changed and why
    TestingExact commands executed & verification results
    Risk / ImpactPotential risks reviewers should watch out for
    Issue linkFixes ID-123 (links PR to issue)
    25
    Code Review Best Practices
    🔍 Code Reviewer Checklist
    • 1. Understand requirement & business scope before reading code.
    • 2. Check logic correctness, edge cases, and error handling.
    • 3. Check security, credential exposure, and SQL injection risks.
    • 4. Verify unit tests and test coverage metrics.
    • 5. Provide constructive, respectful, and actionable feedback.
    26
    Forks and Open-Source Workflow
    🔄 Fork Workflow Flowchart
    Original Repo
    Upstream
    ➔
    Fork
    Your Origin
    ➔
    Feature Branch
    Local Work
    ➔
    Pull Request
    Proposed Changes
    ➔
    Review + Merge
    Integrated Code
    git clone https://github.com/YOU/project.git git remote add upstream https://github.com/OWNER/project.git git fetch upstream git switch main git merge upstream/main git switch -c fix/bug git push -u origin fix/bug
    27
    CODEOWNERS & Repository Templates
    // .github/CODEOWNERS syntax example /api/ @backend-team /frontend/ @frontend-team /docs/ @docs-team /.github/workflows/ @devops-team
    28
    Branch Protection & Rulesets
    Control GatePurpose & Protection
    Require pull requestPrevents uncontrolled direct commits to main
    Required approvalsEnforces peer review gate (e.g. 1 or 2 approvals)
    Required status checksEnforces green CI build & test suite passage before merge
    Code-owner reviewRequires approval from CODEOWNERS for specific paths
    Block force pushesPrevents history rewriting on main branch
    Block deletionProtects critical production branches from accidental deletion
    Created by Gagan Sir
    Module 05: GitHub Actions Architecture, Syntax, Triggers & Matrix
    Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
    29
    GitHub Actions Architecture
    🇬🇧 English Definition
    GitHub Actions is an automated workflow engine integrated into GitHub. Workflows are declared in YAML under `.github/workflows/`. Workflows respond to events, execute jobs on runners, and run sequential steps.
    🇮🇳 Hinglish Definition
    GitHub Actions GitHub ka builtin automation engine hai. Event trigger hone par YAML workflow runner machine par jobs aur steps automatically run karta hai.
    🔄 Actions Architecture Flowchart
    Event
    Push / PR / Cron
    ➔
    Workflow YAML
    .github/workflows/
    ➔
    Jobs
    Runners
    ➔
    Steps
    Actions / Commands
    ➔
    Artifact / Deploy
    Output
    30
    Workflow YAML Syntax & Example
    name: CI on: push: branches: [main] pull_request: permissions: contents: read jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - run: echo "Run tests here"
    31 & 32
    Triggers, Jobs, Steps & Runners
    on: push: branches: [main] pull_request: branches: [main] workflow_dispatch: schedule: - cron: "0 2 * * 1" release: types: [published]
    33
    Contexts and Expressions
    // Useful Context Expressions: ${{ github.ref }} ${{ github.sha }} ${{ github.actor }} ${{ github.repository }} ${{ github.event_name }} ${{ runner.os }} ${{ matrix.node }} ${{ secrets.DEPLOY_KEY }} ${{ vars.APP_ENV }} ${{ needs.build.outputs.version }}
    34
    Conditions, Matrix Builds & Step Outputs
    jobs: test: strategy: fail-fast: false matrix: node: ["20", "22"] os: [ubuntu-latest, windows-latest] runs-on: ${{ matrix.os }} steps: - uses: actions/checkout@v5 - uses: actions/setup-node@v5 with: node-version: ${{ matrix.node }} - run: npm ci - run: npm test
    35
    Artifacts and Dependency Caching
    // Upload Artifact - name: Upload Build Artifact uses: actions/upload-artifact@v4 with: name: build-dist path: dist/ // Download Artifact - name: Download Build Artifact uses: actions/download-artifact@v4 with: name: build-dist path: dist/
    Created by Gagan Sir
    Module 06: Advanced Actions, Service Containers, Security & CI/CD
    Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
    36
    Service Containers (PostgreSQL / Redis Integration Tests)
    jobs: test: runs-on: ubuntu-latest services: postgres: image: postgres:16 env: POSTGRES_PASSWORD: postgres ports: - 5432:5432 options: >- --health-cmd "pg_isready -U postgres" --health-interval 10s --health-timeout 5s --health-retries 5 steps: - uses: actions/checkout@v5 - run: pytest -q
    37
    Reusable Workflows
    // .github/workflows/reusable-ci.yml name: Reusable CI on: workflow_call: inputs: python: required: true type: string jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v5 - uses: actions/setup-python@v6 with: python-version: ${{ inputs.python }} - run: pytest -q // Caller Workflow: jobs: ci: uses: OWNER/REPO/.github/workflows/reusable-ci.yml@v1 with: python: "3.13"
    38
    Composite Actions
    // .github/actions/setup-project/action.yml name: Setup Project description: Common project setup inputs: version: required: true runs: using: composite steps: - uses: actions/setup-python@v6 with: python-version: ${{ inputs.version }} - shell: bash run: pip install -r requirements.txt
    39
    Secrets, Variables and Least-Privilege Permissions
    permissions: contents: read jobs: build: permissions: contents: read steps: - uses: actions/checkout@v5
    40
    Environments and Deployments
    jobs: deploy: runs-on: ubuntu-latest environment: production steps: - uses: actions/checkout@v5 - run: ./scripts/deploy.sh
    41
    Continuous Integration (CI) Pipeline
    🔄 CI Pipeline Flowchart
    Checkout
    Source code
    ➔
    Install
    Dependencies
    ➔
    Lint / Type
    Static checks
    ➔
    Unit Tests
    Pytest/Jest
    ➔
    Security
    Scans
    42
    Continuous Delivery / Deployment (CD) Pipeline
    🔄 CD Pipeline Flowchart
    Build Once
    Artifact / Image
    ➔
    Publish
    Container Registry
    ➔
    Deploy Staging
    Validation
    ➔
    Approve Gate
    Manual Review
    ➔
    Deploy Prod
    Production
    Created by Gagan Sir
    Module 07: Security, APIs, Hooks & Internals
    Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
    43 & 44
    GitHub Security & Dependabot
    // .github/dependabot.yml configuration version: 2 updates: - package-ecosystem: "pip" directory: "/" schedule: interval: "weekly" - package-ecosystem: "npm" directory: "/frontend" schedule: interval: "weekly" - package-ecosystem: "github-actions" directory: "/" schedule: interval: "weekly"
    45 & 46
    Packages & GitHub Releases
    git switch main git pull --ff-only git tag -a v1.0.0 -m "Release 1.0.0" git push origin v1.0.0 // Create release via GitHub CLI with auto notes gh release create v1.0.0 --generate-notes
    47
    GitHub CLI (gh) Command Reference
    gh auth login gh repo clone OWNER/REPO gh issue create gh issue list gh pr create gh pr list gh pr checkout 123 gh pr review 123 --approve gh pr merge 123 gh run list gh run watch
    48 & 49
    GitHub REST API & GraphQL Basics
    // REST API Example via curl curl -L -H "Accept: application/vnd.github+json" -H "Authorization: Bearer $GITHUB_TOKEN" -H "X-GitHub-Api-Version: 2022-11-28" https://api.github.com/repos/OWNER/REPO // GraphQL Query Example query { repository(owner: "OWNER", name: "REPO") { name description stargazerCount } }
    50 & 51
    Webhooks and Local Git Hooks
    // .git/hooks/pre-commit executable shell script // bin/sh ruff check . pytest -q
    52
    Git Internals & Object Model
    🔄 Git Object Model Flowchart
    Commit
    Tree + Parent + Meta
    ➔
    Tree
    Names + Modes + Blobs
    ➔
    Blob
    Raw File Content
    ➔
    Refs
    Branch / Tag Pointers
    git rev-parse HEAD git cat-file -t HEAD git cat-file -p HEAD git count-objects -v git fsck --full
    53 & 54
    Monorepos, Dev Containers & GitHub Pages
    // .devcontainer/devcontainer.json { "name": "Project Dev Environment", "image": "mcr.microsoft.com/devcontainers/python:3.13", "postCreateCommand": "pip install -r requirements.txt" }
    Created by Gagan Sir
    Module 08: Troubleshooting, Projects & 150+ Interview Q&A Bank
    Git Basics + GitHub Workflows + Actions CI/CD + Security + Releases + CLI + REST/GraphQL APIs + 150+ Q&A
    55
    Troubleshooting Reference Guide
    ProblemFirst ChecksLikely Resolution Direction
    Nothing to commitgit status / diffNo changes made or already committed
    Push rejectedgit fetch / logRemote branch has newer history; fetch & integrate
    Authentication failedssh -T / gh auth statusExpired token, wrong URL or missing SSH key
    Merge conflictgit status / diffResolve unmerged conflict paths manually
    Detached HEADgit statusSwitch back to branch or create new recovery branch
    Lost commitgit reflogFind lost SHA in reflog and recreate branch
    Secret detectedRotate credential first!Rotate key, remove from code, remediate git history
    56
    Real Development Workflow
    🔄 Enterprise Development Workflow Flowchart
    Task / Issue
    Planning
    ➔
    Feature Branch
    Development
    ➔
    Commit + Push
    Upload
    ➔
    Pull Request
    Review
    ➔
    CI + Review
    Automated Gate
    ➔
    Merge & Deploy
    Release
    57
    10 Complete Practical Portfolio Projects
    🚀 Practical Projects List
    • 1. Portfolio Website — README + project code + issues + PR + Actions CI
    • 2. Python API Pipeline — Tests + lint + matrix CI + artifact upload
    • 3. Node Application — npm CI + build + release workflow
    • 4. Docker Application — Build image + scan vulnerabilities + publish to GHCR
    • 5. Database Integration — Actions service container (PostgreSQL) + integration tests
    • 6. Release Pipeline — Tag ➔ build ➔ test ➔ GitHub Release
    • 7. Open-Source Contribution — Fork ➔ branch ➔ PR ➔ review
    • 8. DevSecOps Repo — Secret scanning + dependency scanning + protected main
    • 9. Reusable CI Platform — Reusable workflow matrix used by multiple repos
    • 10. Documentation Site — Markdown docs + GitHub Pages publishing workflow
    58 & 59
    150+ Interview Questions & Scenario-Based Answers
    🎯 Key Scenario Answers
    Scenario: Bad commit merged to main? Do not rewrite shared history. Assess impact, revert the bad commit (`git revert SHA`), run CI checks, communicate with team, then fix forward.

    Scenario: Secret committed? Rotate and revoke credentials immediately! Investigate exposure, remove secret from current code, remediate Git history if required, and enable secret scanning push protection.
    60
    Master Command Cheat Sheet
    // DAILY WORKFLOW git status git switch main git pull --ff-only git switch -c feature/name git diff git add . git commit -m "feat: description" git push -u origin feature/name // UNDO & RECOVERY git restore file git restore --staged file git revert SHA git reset --soft HEAD~1 git reset --hard HEAD~1 git reflog // GITHUB CLI gh auth status gh repo clone OWNER/REPO gh issue list gh pr create gh pr checkout 123 gh pr review 123 --approve
    61 & 62
    30/60/90 Day Roadmap & Final Readiness Checklist
    🇬🇧 90-Day Roadmap
    Days 1–15: Git basics, commits, branches, merge, rebase & reflog.
    Days 16–30: GitHub PRs, Code Review, CODEOWNERS & rulesets.
    Days 31–45: Actions YAML workflows, matrix builds & caching.
    Days 46–60: CD pipelines, environments, service containers.
    Days 61–75: DevSecOps, secret scanning, Dependabot & GHCR.
    Days 76–90: CLI, REST/GraphQL APIs, webhooks & monorepos.
    🇮🇳 Golden Rule
    Before executing a destructive Git command, know exactly which history it alters and how you will recover it using reflog or revert!