Git & GitHub Mastery interview questions & answers

Video game ke save points yaad kijiye. Boss fight se pehle aap save karte hain. Mar gaye to poora game dobara nahi khelte - paanch minute pehle wala save load kar lete hain. Aap das save rakh sakte hain aur kisi bhi par wapas ja sakte hain. Ab socha jaaye ki aapka project folder bhi aisa hi chalta: jab bhi kuch sahi chal raha ho, "save point" daba do aur uspar ek line ka note likh do. Ek hafte baad koi change sab kuch tod de, to ghabrane ki jagah aap last good save load kar lete.

Git files ke liye wahi save-point system hai. Sirf code ke liye nahi - text files ke kisi bhi folder ke liye: website, HTML me likha resume, notes, config files.

🌍 Real-world example: Asha ek fresher hai jo apni resume website bana rahi hai. Git ke bina uska folder dheere-dheere ban jaata hai resume.html, resume_new.html, resume_final.html, resume_final_v2.html, resume_final_v2_REAL.html. Use pata nahi hota ki current kaunsi hai, doosri se kya badla, ya recruiter ko mail kaunsi gayi thi. Git ke saath ek hi index.html hoti hai, aur uske peeche save points ki list - har ek par message ("Add intro line"), author aur date. Kuch khota nahi, aur kuch rename nahi karna padta.

💡 version control = ek system jo files ke set me har change ko waqt ke saath record karta hai, taaki aap dekh sakein kya badla, kisne badla, aur wapas ja sakein.

💡 repository (repo) = project folder plus uski poori recorded history. Git history ko project ke andar .git naam ke hidden folder me rakhta hai.

💡 commit = ek save point: us pal par aapki files ka snapshot, message, author aur date ke saath.

💡 distributed = har insaan ke computer par poori history ki full copy hoti hai, sirf latest files nahi.

Standard definition: Git ek free, open-source distributed version control system hai. Wo project ki history ko commits ki series ki tarah record karta hai, branches ke zariye kai logon ko ek hi project par parallel kaam karne deta hai, aur har clone me us history ki poori copy rakhta hai.

Git kaunsi problem solve karta hai

Version control se pehle teams wahi teen bure tareeke use karti thi, aur teeno toot-te hain:

1. Folder copy karke rename karna (final_v2_REAL). Do copies me kya alag hai ye dono kholkar hi pata chalta hai, aur naam ek hafte me bekaar ho jaate hain.
2. Zip email ya WhatsApp karna. Do log ek hi file ek saath edit karte hain, apne versions wapas bhejte hain, aur ab kisi ko haath se merge karna padta hai aur ek insaan ka kaam overwrite ho jaata hai.
3. Shared folder, ek time par ek hi insaan edit kare. Safe hai, par parallel kaam nahi ho sakta aur history phir bhi nahi milti.

Git in teeno ko ek idea se replace karta hai: history hi product hai. Har change ek commit hai, har commit ka author aur message hai, aur do logon ka kaam merge karna ek tool hai, haath ka kaam nahi (merging topic me aap ye karenge).

Git, GitHub nahi hai

Ye beginners ka sabse common confusion hai, aur interviewer pehle paanch minute me ye test karta hai.

	Git	GitHub
Ye kya hai	Aapke computer par install hone wala tool	Ek website / company jo Git repositories host karti hai
Internet chahiye?	Nahi - history aapki disk par hai	Haan
Kab bana	2005, Linus Torvalds ne, Linux kernel development ke liye	Alag company jisne Git ke upar ek service banayi
Kya deta hai	commits, branches, history, merge	repos ka shared ghar, pull requests, issues, code review, Actions
Alternatives	(ye standard hai)	GitLab, Bitbucket, aur bhi

Saboot neeche ke run me hai: poora resume-site demo - teen commits, restore ki hui file, ek clone - bina GitHub, bina account aur bina internet ke hota hai. GitHub tab aata hai jab aap repo doosron ke saath share karna chahte hain.

Ye itihaas Git ki apni documentation me likha hai: 2005 me Linux kernel community ka jis proprietary tool (BitKeeper) tak free access tha wo chhin gaya, to Linus Torvalds aur community ne apna tool banaya. Uske design goals me speed, simple design, hazaaron parallel branches ka strong support, aur fully distributed hona shamil hain.

Run me kya dikha, line by line

Is lesson ke neeche ka terminal output saath-saath padhiye.

1. git init -b main ne ek khaali folder ko repository bana diya. Dikhne me sirf ek hidden .git folder aaya - saari history yahin rahegi.
2. git add phir git commit ne pehla save point banaya. Git ne jawab diya [main (root-commit) 07775e0] Add heading: branch main, commit ki chhoti id 07775e0, aur aapka message. root-commit ka matlab "bilkul pehla commit - iska koi parent nahi".
3. Do aur git commit -am ne do aur save points banaye (-a ka matlab "jo files Git pehle se track karta hai unke mere changes bhi shamil karo" - agle topics me ise theek se samjhaya gaya hai). git log --oneline teeno ko dikhata hai, sabse naya sabse upar, ek line me ek. Chhoti ids aapki machine par alag hongi - wo content, author aur time se nikalti hain.
4. rm index.html ne file delete kar di. git status --short ne D index.html bataya - Git ne dekh liya ki file gayab hai. git restore index.html ne use last commit se wapas la diya, aur cat me teeno lines salaamat hain. Ye hai "save load karne" wala pal.
5. git show HEAD~2:index.html ne file ko waisa dikhaya jaisi wo do commits pehle thi - sirf heading. Aapne kuch badle bina purana version dekh liya. (HEAD ka matlab "jis commit par main abhi hoon"; HEAD~2 uske do commit pehle wala. Branching topic HEAD ko theek se samjhata hai.)
6. git clone resume-site resume-site-copy ne doosri, independent copy banayi, aur uske andar git log --oneline wahi teen commits dikhata hai. Clone ne sirf latest files nahi, poori history copy ki. "Distributed" ka practical matlab yahi hai.

Snapshots, file-by-file changes nahi

Bahut se purane systems project ko "ye file, aur uspar edits ki list" ki tarah store karte hain. Git ki apni documentation uska model alag batati hai: wo apne data ko ek miniature filesystem ke snapshots ki series ki tarah dekhta hai. Commit karte waqt Git record karta hai ki us pal poora project kaisa dikhta hai (aur jo files badli nahi unhe dobara copy nahi karta, purani ko hi reuse karta hai). Ye conceptual hai - disk par Git data ko kaise pack karta hai wo baad ka internals topic hai - par ye aapne abhi jo dekha usse milta hai: purana version dekhna ek snapshot chunna tha, edits ki list replay karna nahi.

Isi documentation ke do aur nateeje:

• Lagbhag sab kuch local hai. Poori history aapki disk par hai, isliye git log, git commit, git diff aur purane waqt me jaane ke liye network nahi chahiye. Aap train me commit kar sakte hain aur baad me share.
• Sab kuch checksum hota hai. Git content ko SHA-1 hash se refer karta hai, 40-character hexadecimal string (upar ka 07775e0 uske pehle 7 characters hain). File badli to hash badal jaata hai - isliye corruption chhup nahi sakti.

Git kahan madad karta hai, aur kahan nahi

Limits dekhne ke liye do cheezein chalayi gayi, ratti nahi:

1. Bade binary files se repo tezi se phoolta hai. Ek 20 MB ki random file commit ki, aur .git 20M naapa gaya. Phir file ko doosri 20 MB random file se badla aur dobara commit kiya: .git 39M nikla. Dono versions hamesha ke liye store hain, kyunki har commit ek permanent snapshot hai. (Random data bilkul compress nahi hota, isliye ye worst case hai - aam files behtar compress hoti hain - par seekh wahi hai: videos, datasets aur installers plain Git me nahi rakhne chahiye. Git LFS isi ke liye hai, power-tools topic me aayega.)

2. Latest commit se secret delete karne se history se delete nahi hota. .env file jisme API_KEY=sk-test-123 tha commit ki, phir agle commit me hata di. Folder ab saaf hai (ls -A sirf .git dikhata hai), phir bhi git show HEAD~1:.env ab bhi API_KEY=sk-test-123 chhapta hai. Repository jiske paas bhi hai wo ise padh sakta hai. Leak hui key ko rotate karna padta hai (provider par badalna), sirf delete karna kaafi nahi - recovery topic me history scrub karna aayega, aur history-and-ignore topic me .env ko pehle hi bahar rakhna.

Kab use karein: jis project ki zindagi me ek se zyada version honge uske liye Git use kijiye: source code, config files, documentation, portfolio site, notes bhi. Agar kabhi ye sawaal aaye "ye pichhle mangalwar kaisa dikhta tha?" ya "ye line kisne badli?", to jawab haan hai. Project ke pehle din se use kijiye, akele kaam karte hue bhi - cost kuch commands ka hai, aur pehli baar jab kuch toot-ta hai tab ye apna daam wasool kar deta hai.

Kab NAHI use karein (sirf Git par bharosa): backup ki tarah (jo repo sirf aapke laptop par hai wo laptop ke saath chala jaata hai - remote chahiye, jaise GitHub), bade binaries ya datasets ke store ki tarah, aur secrets ki jagah ki tarah. Jo files text ki tarah compare ya merge nahi ho sakti (Word document, Photoshop file) unke liye bhi Git galat tool hai - store kar lega, par uski asli taakat, diff aur merge, wahan kaam nahi karti.

Interviewer yahan asal me kya poochte hain

"Git kya hai?", "Git aur GitHub me kya farak hai?" aur "distributed ka kya matlab?" lagbhag har fresher interview me poochhe jaate hain. Strong jawab teen vaakya ka hota hai: Git ek distributed version control system hai jo locally chalta hai aur history ko commits ki tarah record karta hai; GitHub Git ke upar bani hosting service hai jo collaboration (pull requests, issues, CI) jodti hai; aur distributed ka matlab har clone me poori history hoti hai, isliye zyadatar kaam ko network nahi chahiye. Ab aap har vaakya ke peeche kuch aisa rakh sakte hain jo aapne khud chalaya.

git --version
mkdir resume-site && cd resume-site
git init -b main
echo '<h1>Asha Verma</h1>' > index.html
git add index.html
git commit -m "Add heading"
echo '<p>Fresher, Pune</p>' >> index.html
git commit -am "Add intro line"
echo '<p>Skills: HTML, CSS</p>' >> index.html
git commit -am "Add skills"
git log --oneline
rm index.html
git status --short
git restore index.html
cat index.html
git show HEAD~2:index.html
cd ..
git clone resume-site resume-site-copy
cd resume-site-copy
git log --oneline

Socha jaaye ki aap naye office join kar rahe hain. Koi kaam shuru karne se pehle HR ko aapke ID card par do cheezein chahiye: aapka naam aur email. Uske baad aap jo bhi file chhuyenge aur jis bhi register par sign karenge, usme wahi naam hoga. Git bhi yahi karta hai. Pehle commit se pehle aap Git ko batate hain ki aap kaun hain - kyunki Git jo bhi commit record karta hai uspar author ka naam aur email lagta hai.

Isliye Git setup karna chaar chhote kaam hain, jo har computer par ek baar hote hain: install karna, Git ko batana ki aap kaun hain, default branch ka naam chunna, aur ek repository shuru karna (ya copy karna).

🌍 Real-world example: Asha ko pehli job me naya laptop milta hai. Wo Git install karti hai, teen git config --global commands (naam, email, default branch) chalati hai, aur phir kabhi unke baare me nahi sochti. Pehle hafte me: company ka project git clone karna, aur apne practice folder ke liye git init. Agar wo identity wala step chhod deti, to uska bilkul pehla commit Author identity unknown ke saath fail ho jaata - jo aap neeche dekhenge.

💡 config = Git ki settings. Ye plain text files me rehti hain, teen level par (system, global, local), aur zyada specific level general level ko override karta hai.

💡 git init = "is folder ko repository bana do" - hidden .git folder banata hai.

💡 git clone = "kisi maujooda repository ko, poori history ke saath, mere computer par copy kar do".

💡 origin = jis jagah se aapne clone kiya, Git us jagah ko jo default nickname deta hai.

Standard definition: git config Git ki settings padhta aur likhta hai; git init maujooda folder me ek naya, khaali repository banata hai; git clone kisi maujooda repository ki copy banata hai, uski saari history ke saath, aur ye yaad rakhta hai ki wo kahan se aayi - remote origin ke naam se.

Step 1 - Install karein aur check karein

Git ko Pro Git book me di gayi official sources se install kijiye:

OS	Kaise
Windows	git-scm.com/download/win se installer download kijiye (ye "Git for Windows" project hai). Community-maintained Chocolatey package bhi hai
macOS	Terminal me git --version chalaiye - macOS 10.9 ya naye par Git na ho to ye Xcode Command Line Tools install karne ka offer deta hai. Ya git-scm.com/download/mac ka installer
Linux	sudo apt install git-all (Debian/Ubuntu) ya sudo dnf install git-all (Fedora/RHEL)

Ye install steps Pro Git book se hain aur yahan chalaye nahi gaye - is course ki machine par Git pehle se install tha. Jo chalaya gaya wo check hai: git --version ne git version 2.43.0.windows.1 chhapa. Agar ye command version dikhaye to ho gaya; "command not found" aaye to install poora nahi hua ya terminal dobara kholna padega.

Version note: ye course Git 2.43 par chalaya gaya hai. Course me aage do cheezein minimum version maangti hain, aur jahan use hoti hain wahan flag ki gayi hain: git init -b aur init.defaultBranch setting Git 2.28 (2020) me aaye, aur git switch / git restore Git 2.23 me. Kisi command ko doshi thehrane se pehle git --version se apna version dekh lijiye.

Step 2 - Git ko batayein ki aap kaun hain

Pehle dekhiye ki na batane par kya hota hai. Ek fresh repository me, jahan identity configure nahi thi, git commit -m "first" exit code 128 ke saath ruk gaya:

Author identity unknown

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'asha@my-laptop.(none)')

(Aakhri line ka text aapka username aur computer ka naam hota hai; yahan badal diya gaya.) Git andaza lagane se mana karta hai. Fix wahi do commands hain jo message me hain, aur neeche wali teesri setting - aur is lesson ka run bilkul yahi karta hai.

Git itna zor kyun deta hai? Har commit me author ka naam aur email record hota hai. Poora git log (--oneline ke bina) har commit ke liye Author: aur Date: line chhapta hai. GitHub aapki Git configuration ke email ka use karke command line se push kiye gaye commits ko aapke GitHub account se jodta hai - isliye wahi email address use kijiye jo aapne apne GitHub account me add kiya hai, warna aapke commits aapke naam par nahi dikhenge aur contributions graph me nahi aayenge (GitHub ki commit email addresses wali documentation ke mutabik). Agar aap public history me apna asli email nahi chahte, to GitHub ek noreply address bhi deta hai jo aap use kar sakte hain.

Zaroori - ye label hai, login nahi. Git ise verify nahi karta. Run me -c user.name="Someone Else" -c user.email="boss@bigcorp.example" ke saath commit kiya aur git log ne khushi se Someone Else <boss@bigcorp.example> not really me chhapa. Koi bhi koi bhi naam likh sakta hai. (Commit kisne likha ye saabit karna commit signing ka kaam hai, jo baad me GitHub authentication ke saath aayega.) Asli access control wo password, token ya SSH key hai jo aap GitHub se baat karte waqt use karte hain.

Step 3 - Default branch ka naam

Aisi machine par git init chalaiye jahan init.defaultBranch kabhi set nahi hua, to Git 2.43 ek lamba hint chhapta hai:

hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>

aur git status phir On branch master kehta hai. Git ki apni git init documentation kehti hai ki fallback abhi master hai aur Git 3.0 release hone par main ho jaayega. GitHub aur zyadatar teams pehle se main use karti hain, isliye ise ek baar explicitly set kar dijiye - git config --global init.defaultBranch main - aur har naya repository bina hint ke main par shuru hoga. Neeche ke run me pehla git status sahi me On branch main kehta hai.

Step 4 - Apni configuration dekhein aur samjhein

git config --global --list ne bilkul wahi teen lines chhapi jo humne set ki thi:

user.name=Asha Verma
user.email=asha@example.com
init.defaultbranch=main

Dhyan dijiye Git key ko lowercase me dikhata hai (init.defaultbranch) - Git keys isi tarah chhapta hai; aapne jaise likha, init.defaultBranch, wo bhi waisa hi chalta hai.

Git me settings ke teen ghar hain, aur git config ek flag se unme se ek chunta hai (git config -h me --system, --global, --local aur --worktree dikhte hain):

Flag	Kispar lagta hai	Kahan store hota hai
--system	is computer ke har user par	ek system-wide file (is Windows machine par: C:/Program Files/Git/etc/gitconfig)
--global	aap par, har repo me	home folder ki .gitconfig (yahan: C:/Users/<you>/.gitconfig)
--local (repo ke andar git config default me yahi likhta hai - run: bina flag ka git config demo.key v1 .git/config me gaya)	sirf is repository par	.git/config

Zyada specific wala jeetta hai. Run saabit karta hai: globally user.email = asha@example.com hote hue, git config --local user.email "asha.work@example.org" ke baad git config user.email ne asha.work@example.org chhapa. git config --show-origin --get-all user.email dono values aur har ek kahan se aayi dikhata hai - global file aur .git/config. Phir git config --local --unset user.email ne override hata diya aur jawab wapas asha@example.com ho gaya. Company ke repo me work email aur baaki sab jagah personal email isi tarah chalta hai. (--system run me nahi chalaya gaya; uska order me sthaan Git documentation se hai.)

Kaun sa scope, kab: --global un cheezon ke liye jo aapke baare me sach hain (naam, personal email, default branch, editor, aliases). --local (repo ke andar bas flag chhod dijiye) un cheezon ke liye jo is project ke baare me sach hain (kisi ek company repo ka work email). --system se tab tak door rahiye jab tak aap machine administer na karte hon.

Usi run ki ek kaam ki setting: git config --global alias.st "status --short --branch" se git st shortcut ban gaya. Aliases sirf aapki apni machine ke shortcuts hain.

Step 5 - git init: repository shuru karein

Run me: mkdir hello-git && cd hello-git, phir git init. Git ne jawab diya Initialized empty Git repository in ~/hello-git/.git/. Phir git status ne chhapa:

On branch main

No commits yet

nothing to commit (create/copy files and use "git add" to track)

Ise aise padhiye: aap branch main par hain, abhi koi history nahi hai, aur Git ko track karne ko kuch dikh nahi raha. echo 'hello git' > notes.txt, git add notes.txt aur git commit -m "First commit" ke baad log me ek commit hai.

Hidden .git folder hi repository hai. ls -A .git ne COMMIT_EDITMSG config description HEAD hooks index info logs objects refs dikhaya. Inhe haath se edit nahi karte; internals topic inhe kholega. Abhi bas ek cheez yaad rakhiye: .git poori history hai. Use delete kar do to folder phir se sirf normal files rah jaata hai, har commit gayab. (Ye chalaya nahi gaya - ye is baat ki definition hai ki .git me kya hai.) Kisi problem ko "theek karne" ke liye ise kabhi delete mat kijiye; jis project ki koi aur copy nahi (na remote, na backup) usme .git delete karna undo nahi ho sakta.

Maujooda repository me git init dobara chalana safe hai: run me Reinitialized existing Git repository chhapa aur kuch nahi badla.

Jaanne layak galti - galat folder me git init. Run me ek maujooda repository ke andar sub/ banaya, wahan git init chalaya, aur wapas bahar wale repo me aaye. Bahar wale git status --short ne ?? sub/ (untracked) dikhaya, aur git add sub fail hua: error: 'sub/' does not have a commit checked out / fatal: adding files failed. Ab aapke paas repository ke andar repository hai, jise Git ek special case maanta hai. Ye dikhe to lagbhag hamesha aapne git init ek folder zyada andar (ya galat jagah) chalaya tha. Agar pakka nahi ki folder pehle se kisi repository ke andar hai ya nahi, to git init se pehle git status chalaiye.

Step 6 - git clone: maujooda repository copy karein

git clone hello-git hello-copy ne hello-copy/ banaya jisme files aur poori history wala .git folder hai. (Yahan source ek local folder tha taaki demo ko network na chahiye; asli zindagi me ye URL hota hai, jaise GitHub ka HTTPS ya SSH address - authentication topic unhe cover karta hai.) Clone ke andar:

• git remote -v ne do lines chhapi: origin ~/hello-git (fetch) aur origin ~/hello-git (push). origin wo nickname hai jo Git ne us jagah ko diya jahan se clone aaya, aur wo yaad rakhta hai ki kahan se fetch karna aur kahan push karna hai.
• git status ne chhapa Your branch is up to date with 'origin/main' aur working tree clean - clone ki main pehle se origin ki main se judi hai.

git clone <source> <name> folder ka naam chunne bhi deta hai; doosra argument na do to Git repository ka apna naam use karta hai.

git init vs git clone: git init tab jab project abhi exist hi nahi karta (aap apne computer par scratch se shuru kar rahe hain). git clone tab jab wo kahin pehle se exist karta hai (company repo, open-source project, GitHub par aapka apna repo) - ek command me aapko files aur history aur origin link milta hai. git init karke maujooda project ki files copy mat kijiye: files hongi par history nahi.

Config --global vs --local kab: global us ke liye jo aap hain, local us ke liye jo ek project me khaas hai (Step 4 dekhiye). Inhe mila dene se aam taur par commit galat email ke saath dikhta hai.

Kab NAHI use karein (sirf config par bharosa): user.name aur user.email authentication nahi hain aur authorship ka saboot nahi hain - koi bhi unhe kuch bhi set kar sakta hai, jaisa Someone Else run ne dikhaya. Commit ke author field ko kabhi is baat ka saboot mat maniye ki asal me kisne likha.

Interviewer yahan kya poochte hain

"Git pehli baar kaise set up karte hain?" (install, git config --global user.name, user.email), "git init aur git clone me kya farak hai?", "Git config ke teen levels kaun se hain?" aur "Git apna data kahan rakhta hai?" (.git folder). In sab ka ek chhota jawab hai jise ab aap ek run se back kar sakte hain.

git --version
git config --global user.name "Asha Verma"
git config --global user.email "asha@example.com"
git config --global init.defaultBranch main
git config --global --list
mkdir hello-git && cd hello-git
git init
git status
echo 'hello git' > notes.txt
git add notes.txt
git commit -m "First commit"
git log --oneline
ls -A .git
git config --local user.email "asha.work@example.org"
git config --show-origin --get-all user.email
git config user.email
git config --local --unset user.email
git config user.email
cd ..
git clone hello-git hello-copy
cd hello-copy
git remote -v
git status

Aap kya banayenge: ek chhota portfolio page jo Git repository me rehta hai, do arthpurn commits aur ek aur commit ki saaf history ke saath, aur uski ek copy remote par - wahi raasta jo aap kisi project ko GitHub par daalne ke liye lete hain. Aapko kya chahiye: Git install ho aur doosre topic ka setup ho. Aur kuch nahi: yahan use hua har command pehli baar aate hi samjhaya gaya hai, isliye aap ye project topic 1 aur 2 ke turant baad kar sakte hain.

Remote ke baare me ek note. GitHub par push karne ke liye aapka GitHub account aur login chahiye, jo script me dikhaya nahi ja sakta. Isliye ye project ek local stand-in use karta hai: git init --bare github-stand-in.git se bana doosra folder jo connection ke GitHub wale side ki tarah behave karta hai. Remote ke liye jo bhi command aap type karte hain wo asli GitHub jaisa hi hai; sirf address alag hai. Aakhri section batata hai ki GitHub ke liye kya badalna hai (GitHub ki documentation se, yahan chalaya nahi).

🌍 Real-world example: Asha ek fresher hai jiske laptop par aadha bana portfolio page hai. Ek recruiter link maangta hai. Agar page sirf folder me hai, to laptop ke saath kho sakta hai aur koi use dekh nahi sakta. Is project ke ant tak uski history hai, remote par copy hai, aur wo roz ka loop - change, commit, push - hai jo wo apne poore career me dohrayegi.

Step 0 - Git ko batayiye aap kaun hain (har computer par ek baar)

git config --global user.name "Asha Verma"
git config --global user.email "asha@example.com"
git config --global init.defaultBranch main

Apna naam aur email use kijiye. Ye doosra topic hai; pehle kar chuke hon to skip kijiye. Iske bina aapka pehla commit Author identity unknown ke saath ruk jaata hai.

Step 1 - Folder ko repository banaiye

mkdir my-portfolio && cd my-portfolio ne project folder banaya aur usme gaya. git init ne Initialized empty Git repository in …/.git/ chhapa - Git ne ek hidden .git folder banaya, jahan wo history rakhta hai. git status ne On branch main, No commits yet aur nothing to commit (create/copy files and use "git add" to track) chhapa: aap branch main par hain, aur abhi koi history nahi.

Step 2 - Pehli files likhiye

Teen files banayin: index.html (aapke naam ka heading aur ek line ka intro), README.md (title aur ek vaakya) aur .gitignore (un files ki list jinhe Git kabhi track na kare - .DS_Store, node_modules/ aur *.log). git status ne ab teeno ko Untracked files ke neeche list kiya: wo folder me hain, par Git unhe abhi record nahi kar raha.

Step 3 - Stage aur commit

Git history do chaalon me record karta hai. git add chunta hai ki agle snapshot me kya jaayega (box me cheezein rakhne jaisa); git commit box ko message ke saath seal karta hai.

• git add index.html README.md .gitignore, phir git status ne Changes to be committed: chhapa jisme teeno files new file: ke saath thin.
• git commit -m "Add portfolio page, README and .gitignore" ne [main (root-commit) 1186a30] Add portfolio page, README and .gitignore aur 3 files changed, 14 insertions(+) chhapa. 1186a30 commit ki chhoti id hai (aapki alag hogi); root-commit ka matlab "bilkul pehla commit".
• git log --oneline ne ab tak ki history list ki: ek line.

Achha message batata hai ki commit kya karta hai, ek chhote vaakya me jo kriya se shuru ho ("Add …", "Fix …"). Chhe mahine baad aap khud ko dhanyavaad denge.

Step 4 - Doosra, chhota commit

index.html me ek Projects section joda gaya. git diff ne exactly chhapa ki kya badla (+ se shuru hone wali do lines). Phir git add index.html aur git commit -m "Add a Projects section" ne [main cb3dd93] Add a Projects section aur 1 file changed, 2 insertions(+) chhapa. git log --oneline ne ab do commits dikhaye, naya pehle: cb3dd93 Add a Projects section, 1186a30 Add portfolio page, README and .gitignore ke upar.

Chhote commits jo har ek ek hi kaam karein - ye wo aadat hai jo abhi banaiye: unhe padhna, review karna aur undo karna aasaan hota hai.

Step 5 - Remote jodiye

Remote kahin aur rakhi aapki repository ki doosri copy hai; aam naam origin hai. Run ne stand-in git init --bare github-stand-in.git se banaya (bina working folder wali repository, jaise servers repositories store karte hain), my-portfolio me wapas gaya aur git remote add origin ../github-stand-in.git chalaya. git remote -v ne origin ../github-stand-in.git (fetch) aur (push) chhapa - wo address jisse Git download aur upload karega.

Step 6 - Pehla push

git push -u origin main ne branch 'main' set up to track 'origin/main'. aur * [new branch] main -> main chhapa. Push aapke commits ko remote par upload karta hai; -u aapki local main ko remote ki main se jodta hai, isliye ab se seedha git push ya git pull jaanta hai kahan jaana hai. git status ne phir kaha Your branch is up to date with 'origin/main', aur git branch -vv ne * main cb3dd93 [origin/main] Add a Projects section chhapa - square brackets link dikhate hain.

Step 7 - Saabit kijiye ki chal gaya

Address wala koi bhi ab aapka kaam le sakta hai. git clone github-stand-in.git proof-clone ne remote se naya folder banaya; ls proof-clone ne index.html aur README.md list kiye (.gitignore hidden file hai, isliye ls use chhupata hai), aur git -C proof-clone log --oneline ne wahi do commits dikhaye. (git -C <folder> … bas command ko aise chalata hai jaise aap us folder ke andar hon.) Jab bhi shak ho "mera push sach me chala?", ye test use kijiye: use kahin aur clone karke dekhiye.

Step 8 - Roz ka loop

Edit, commit, push. sed ne intro line ko Git ka zikr karne wala banaya; git status -s ne M index.html chhapa (modified, abhi commit nahi). git commit -am "Mention Git in the intro" ne use commit kiya - -a ka matlab "jo files Git pehle se track karta hai unke mere changes shamil karo", isliye edit ke liye alag git add nahi chahiye tha. git push ne cb3dd93..9058662 main -> main chhapa. Doosre folder me git pull ne use download kiya (Fast-forward) aur uske git log --oneline ne teen commits dikhaye, sabse naya 9058662 Mention Git in the intro.

Checklist - "ho gaya" kaisa dikhta hai

Ye my-portfolio me chalaiye; aapko ye dikhna chahiye:

• git status -sb ## main...origin/main chhapta hai (na ahead na behind, kuch modified nahi).
• git rev-parse HEAD origin/main | uniq | wc -l 1 chhapta hai - aapka latest commit aur remote ka wahi commit hain.
• git ls-files bilkul .gitignore, README.md, index.html list karta hai.
• git log --oneline saaf messages ke saath teen commits dikhata hai.
• Remote ke fresh clone me wahi files aur wahi teen commits hain.

Asli GitHub use karna (GitHub ki documentation se - chalaya nahi)

1. GitHub par my-portfolio naam ki nayi repository banaiye aur use khaali rakhiye - "Add a README file", .gitignore ya licence tick mat kijiye. GitHub ke "Create repository" form me README option hai; use tick karne par GitHub pehla commit bana deta hai aur aapka pehla push reject ho jaata hai kyunki aapki aur uski history alag hain (baad ka topic fix dikhata hai).
2. Repository ka address copy kijiye (HTTPS wala https://github.com/<you>/my-portfolio.git hai).
3. git remote add origin <wo address> aur git push -u origin main chalaiye - upar jaise hi do commands.
4. GitHub ki documentation kehti hai ki HTTPS par Git aapka username maangta hai aur password ki jagah personal access token (Git ke liye account passwords ab accept nahi hote); doosra tareeka SSH key hai. Ye project login ki details me nahi jaata; course ka ek baad ka topic dono samjhata hai, aur GitHub ki apni documentation bhi remote URLs aur personal access tokens par ye cover karti hai.

Kuch galat ho to

• Pehle commit par Author identity unknown: Step 0 kijiye.
• File edit karne ke baad nothing to commit: shayad aap galat folder me hain (pwd), ya file .gitignore se ignore ho rahi hai.
• fatal: 'origin' does not appear to be a git repository: aapne git remote add origin … chhod diya, ya address galat type kiya (git remote -v dikhata hai Git ke paas kya hai).
• Push reject hua: kisi ne (ya aapne website par) remote par aisa commit rakha jo aapke paas nahi. Force mat kijiye; baad ka topic dikhata hai ki dono ko surakshit tareeke se kaise milate hain.

Aage badhne ke liye

Ek doosra page about.html jodiye aur use alag commit kijiye; .gitignore me ek line jodiye aur check kijiye ki uske match wali file git status me nahi aati; commit message me typo kijiye aur push se pehle dekhiye ki use kaise theek karte hain (wo undo topic me hai); phir apni repository ko teesri baar clone karke confirm kijiye ki history match karti hai.

git config --global user.name "Asha Verma"
git config --global user.email "asha@example.com"
git config --global init.defaultBranch main
mkdir my-portfolio && cd my-portfolio
git init
git status
printf '<!doctype html>\n<html>\n<head><title>Asha Verma</title></head>\n<body>\n<h1>Asha Verma</h1>\n<p>Fresher. Learning web development.</p>\n</body>\n</html>\n' > index.html
printf '# my-portfolio\n\nMy first Git project.\n' > README.md
printf '.DS_Store\nnode_modules/\n*.log\n' > .gitignore
git status
git add index.html README.md .gitignore
git status
git commit -m "Add portfolio page, README and .gitignore"
git log --oneline
printf '<h2>Projects</h2>\n<ul><li>Cafe menu page</li></ul>\n' >> index.html
git diff
git add index.html
git commit -m "Add a Projects section"
git log --oneline
cd ..
git init --bare github-stand-in.git
cd my-portfolio
git remote add origin ../github-stand-in.git
git remote -v
git push -u origin main
git status
git branch -vv
cd ..
git clone github-stand-in.git proof-clone
ls proof-clone
git -C proof-clone log --oneline
cd my-portfolio
sed -i 's#Fresher. Learning web development.#Fresher. Learning Git and web development.#' index.html
git status -s
git commit -am "Mention Git in the intro"
git push
git log --oneline
git -C ../proof-clone pull
git -C ../proof-clone log --oneline
git status -sb
git rev-parse HEAD origin/main | uniq | wc -l
git ls-files