Interactive rebase yadda yake aiki?

Question

Accepted Answer

**Interactive rebase** (`git rebase -i`) yana ba ka damar **sake rubuta, sake tsara, haɗa, gyara, ko cire commits** — tsabtawa jajiya commits kafin ki baje shi. Kaya mai iko don yin tsabtaccen, logical jajiya daga aiki masu gudummawa-aiki-wacce-ke-tafiya commits. ## Fara interactive rebase ```bash git rebase -i HEAD~4 # interactively rebase the last 4 commits git rebase -i # rebase commits after # → opens an editor listing the commits with actions to apply ``` ## Ayyukan ```text pick abc123 Add login form # keep the commit as-is squash def456 Fix typo # COMBINE into the previous commit (merge messages) fixup ghi789 Fix another typo # combine into previous, DISCARD this message reword jkl012 Add validation # keep the commit but EDIT its message edit mno345 Refactor auth # PAUSE to amend the commit (change content) drop pqr678 Debug logging # DELETE this commit entirely # reorder lines to REORDER commits ``` Ka gyara jerin — zaɓi aiki ga kowane commit (da sake tsara layukan ta sake tsara commits) — sannan Git ya sake taɓa shi akasin daidai. ## Amfani da yawanci ```text ✓ SQUASH multiple WIP commits into one clean commit ("wip", "fix", "oops" → one good commit) ✓ REWORD bad commit messages ✓ REORDER commits into a logical sequence ✓ DROP unwanted commits (debug code, mistakes) ✓ SPLIT a commit (via edit) into smaller commits → Result: a clean, logical history instead of messy development commits. ``` ## Golden rule ya ci gaba a aiki ```text ⚠️ Interactive rebase REWRITES history (new commit hashes): → only do it on LOCAL, UNPUSHED commits — never on shared/public history → typical use: clean up your feature branch BEFORE pushing/opening a PR ``` ## Dalilin da ya sa ya matuwa Nisantawa interactive rebase yana da muhimmanci don **yin tsabtaccen jajiya commits**, don haka yana da amfani, ilimin aiki na gaske don aiki na Git na kasuwa. A lokacin haɓaka, commits mahimmanci ne — wacce-ke-tafiya commits da saƙo kamar "wip", "gyara typo", "oops", debug commits, da tsari mara logic — da **interactive rebase** yana ba ka damar **tsabtawa wannan kafin ki baje shi**: tsarawa commits mahimmanci da dumi a cikin tsabtacce logical daya, sake cewo mMessage masu daidaituwa, sake tsara commits a jerin mai hankali, cire commits masu kasa (kamar debug code), da raba commits — canzawa jajiya haɓaka maci a cikin tsabtaccen, logical, bincikeccen jeri. Han ya matuwa ne saboda tsabtaccen jajiya commits (kamar ana baje a bugun kirkirewa-gyara) yana sauƙi bincike damla, jajiya ta fi fahimmawa, da debugging (via bisect) ta fi aiki — saboda haka ƙarfin nadata kafin sauran mutane suka ga aikinka muhimmaci ne a gida na kasuwa Git practice. Nisantawa **ayyukan** (pick, squash, fixup, reword, edit, drop, da sake tsara) da **amfani da yawanci** (musamman squashing WIP commits, pangan lallai da yawa) ita ce sana'ar aiki ta zahiri. Da gareshi, **golden rule na rebasing ya ci gaba a aiki** — interactive rebase ya sake rubuta jajiya (sababbi hashes), don haka dole a yi shi ne akan **local, unpushed commits** (kada a yi shi akan jajiya da aka raba), tare da amfani na yawanci shine tsabtawa feature branch *kafin* pushing ko buɗe pull request. Saboda tsabtaccen, logical jajiya commits yana da daraja don haɗi gida da tsara, da saboda haɓaka ta zahiri tana samarwa commits masu dagewa da interactive rebase zai iya tsabta kafin ki baje shi (sanid, akan local commits), nisantawa interactive rebase — ayyukan, amfani da yawanci kamar squashing, da nau'i-nau'i na aminci — iya muhimmanci, Git ilimin da aka jera a zahiri don kasuwa haɓaka, kaya mai iko don gabatar da tsabtaccen, bincikeccen jajiya wanda ya baje masu tunani Git masu amfani, an amfani shi a yau-yau don shafe aiki kafin an baje shi tare da gida.