Unaweza kurejesha commits zilizopotea kwa kutumia git reflog?

Question

Accepted Answer

**git reflog** inarekodia mahali ambapo HEAD ya tawi lako imekuwa — kila commit, checkout, reset, rebase, n.k. Ni wavu wa usalama kwa **kurejesha commits "zilizopotea"** (baada ya reset mbaya, rebase iliyokosewa, au kufuta tawi) ambazo zinasemekana zimepotea lakini bado zinaweza kurekebishwa.

## Reflog ni nini

```text
The REFLOG logs every movement of HEAD (and branch tips) in YOUR local repo:
  → every commit, checkout, reset, rebase, merge, etc. is recorded with a reference
  → it's LOCAL and includes commits not reachable from any branch (the "lost" ones)
→ Even if you reset/rebase away commits, reflog remembers where they were.
```

## Kurejesha kazi iliyopotea

```bash
git reflog                     # show the history of HEAD movements
# example output:
#   abc123 HEAD@{0}: reset: moving to HEAD~3
#   def456 HEAD@{1}: commit: Important work    ← the "lost" commit!
#   ...

# recover: the lost commit is def456 — get it back
git checkout def456            # inspect it
git branch recovered def456    # create a branch at it (save it)
# or reset back to it:
git reset --hard def456        # restore HEAD to that commit
```

Wakati commits zinasemekana zimepotea (baada ya `reset --hard`, rebase iliyokosewa, au kufuta tawi), `git reflog` inaonyesha mahali ambapo HEAD ilikuwa, na unaweza kurejesha commit kwa hash yake (kuichekeza, kuunda tawi, au kuirejesha kwake).

## Matukio ya kawaida ya kurejesha

```text
✓ After git reset --hard (discarded commits) → find them in reflog, reset back
✓ After a bad rebase (rewrote/lost commits) → reflog has the pre-rebase state
✓ After deleting a branch → its last commit is in reflog → recreate the branch
✓ "Detached HEAD" commits that seem orphaned → reflog finds them
→ As long as commits existed locally, reflog usually can recover them (until GC, ~weeks).
```

## Kwa nini ni muhimu

Kufahamu `git reflog` ni muhimu kama **wavu wa usalama kwa kurejesha kazi iliyopotea**, kwa hivyo ni ujuzi wa vitendo muhimu ambao unaweza kukuokoa kutokana na makosa yanayosemekana kuwa mabaya sana.

Operesheni za Git ambazo zinaandika upya historia au kusonga HEAD — `reset --hard`, rebases zilizokosewa, kufuta matawi — zinaweza kufanya commits **kuonekana kuwa zimepotea**, ambayo ni ya kukamatia macho na inaonekana kuwa haiwezi kurekebishwa.

Hakika muhimu ni kwamba commits hizi kawaida **sio kweli zimepotea**: `git reflog` inarekodia kila harakati ya HEAD ndani ya ndani (kila commit, checkout, reset, rebase), ikiwa ni pamoja na commits ambazo hazireacheable tena kutoka kwa tawi lolote, kwa hivyo inakumbuka mahali ambapo commits "zilizopotea" zilikuwa.

Hii inafanya reflog kuwa **zana yenye nguvu ya kurejesha** — wakati kazi inaonekana kuwa imepotea baada ya reset mbaya, rebase iliyokosewa, au kufuta tawi, unaweza kutumia `git reflog` kupata hash ya commit na kuirejesha (kuichekeza, kuunda tawi kwake, au kuirejesha kwake).

Kufahamu **matukio ya kawaida ya kurejesha** (kurejesha baada ya `reset --hard`, rebases mbaya, kufuta tawi, na commits za kupokeana za detached-HEAD) na kwamba kurejesha kunafanya kazi maadamu commits zilipo ndani ya ndani (hadi kwa garbage collection, kawaida wiki kadhaa baadaye) ni ujuzi wa vitendo muhimu.

Wavu huu wa usalama ni rahisi na ni muhimu kwa kweli — inamaanisha kuwa "Nilizipoeza kazi yangu!" matukio mengi yanaweza kurekebishwa, kuondoa hofu nyingi kuhusu operesheni za rewriting historia za Git.

Kwa kuwa makosa yanayosemekana kuwa yanazipoeza commits ni ya kawaida (hasa wakati wa kujifunza au kwa kutumia amri zenye nguvu kama reset na rebase), na kwa kuwa reflog ni zana ambayo inazirejeza (mara nyingi ikibadilisha hofu kuwa fix haraka), kufahamu `git reflog` — kile kinachorekodia, jinsi ya kurejesha commits zilizopotea, na matukio ya kawaida ya kurejesha — ni ujuzi muhimu wa vitendo wa Git kama wavu wa usalama muhimu, zana inayotoa ujinga kutumia mwenyewe GitOperesheni yenye nguvu na ujuzi unaofariji kwa ajili ya kila waendelezi.