Yaya za ka dawo da commits da ka sata ta hanyar git reflog?

Question

Accepted Answer

**git reflog** yana yin rikodin inda HEAD na reshen ka ya kasua — kowane commit, checkout, reset, rebase, da sauransu. Shine gida mai kariya don **dawo da "commits da aka sata"** (bayan reset mara kyau, rebase mara kyau, ko share share) da suke bayyananne an sata su amma har yanzu akwai damar dawo da su.

## Me reflog ke

```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.
```

## Dawo da aiki da aka sata

```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
```

Lokacin da commits suke bayyananne an sata su (bayan `reset --hard`, rebase mara kyau, ko share share), `git reflog` yana nuna inda HEAD ya kasua, kuma za ka iya dawo da commit-in ta hanyar hashen sa (duba shi, yin saro, ko komawa ga shi).

## Scenarios na dawo da sauransu

```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).
```

## Me ya sa ya zama muhimmi

Sanin `git reflog` yana da daraja azaman **gida mai kariya don dawo da aiki da aka sata**, saboda haka yana da mahimmanci ilimi na aji da zai iya ciyar ka daga kuskuri da suka bayyananne ba tare da dawo ba.

Ayyukan git da ke sake rubuta tarihi ko motsa HEAD — `reset --hard`, rebases mara kyau, share shares — za su iya sa commits **su bayyananne an sata su**, wanda yana bada tsoro kuma yana da alama ba tare da dawo ba.

Mahimmin gaskiya shine cewa wadannan commits galibi **ba a sata su gaske ba**: `git reflog` yana yin rikodi na kowane motsi na HEAD a gida (kowane commit, checkout, reset, rebase), harsu da commits da ba za a iya samun su ta wata reshe ba, saboda haka yana tuna inda commits da "aka sata" su kasua.

Wanan shi ne **kayan dawo da aiki** mai karfi — lokacin da aiki ya bayyananne an sata shi bayan reset mara kyau, rebase mara kyau, ko share share, za ka iya amfani da `git reflog` don nemo hashen commit kuma dawo da shi (dubin shi, yin saro a shi, ko komawa ga shi).

Sanin **scenarios na gida don dawo da aiki** (dawo bayan `reset --hard`, rebases mara kyau, share share, da orphaned detached-HEAD commits) da cewa dawo ya aiki har yanzu kula da commits da aka yi a gida (har zuwa garbage collection, jiya da gida) shine ilimi mai daraja na aji.

Wanan gida mai kariya yana ba da gamsuwa kuma yana da aiki gaske — yana nuna cewa yawancin "na sata aikin!" yanayin za a iya dawo da shi, mun kawar da tsoron da yake kewaye da ayyukan Git na sake rubuta tarihi.

Tun gaske cewa kuskuri da suke bayyananne sun sata commits suna kusan (musamman lokacin koyi ko amfani da ayyukan masu karfi kamar reset da rebase), kuma tun reflog shine kayan da ya dawo da su (galibi yana juyar da ranar tahi zuwa gyara mara haka), sananin `git reflog` — me ya yi rikodin, yaya za ka dawo da commits da aka sata, da scenarios na gida don dawo da aiki — shine ilimi mai daraja na aji Git, gida mai kariya, kayan da ba tare da dogaruwa ba don amfani da ayyukan Git da masu karfi sanin cewa aiki da aka sata za a iya dawo da shi kusan, kuma ilimi mai dashen shuni don kowane mai buga.