---
title: "Discussion on \"Git Recover Lost Commits: 12 Fixes for Common Mistakes\" | Hashnode"
description: "Discussion on \"Git Recover Lost Commits: 12 Fixes for Common Mistakes\". Originally published on DevToolHub.\n\n\nTo git recover lost commits, run git reflog, find the hash from before the mistake, and point a branch at it with git branch rescue <hash>. Almost every local Git"
url: "https://hashnode.com/posts/git-recover-lost-commits-12-fixes-for-common-mistakes/6af7160c63c66a538700c037"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Git Recover Lost Commits: 12 Fixes for Common Mistakes](https://devtoolhub.hashnode.dev/git-recover-lost-commits-12-fixes-for-common-mistakes?utm_source=hashnode&utm_medium=feed)

Originally published on DevToolHub. To git recover lost commits, run git reflog, find the hash from before the mistake, and point a branch at it with git branch rescue <hash>. Almost every local Git

7h ago · 8 min read · devtoolhub.hashnode.dev  
Read the article

-   [#git](https://hashnode.com/tag/git)
-   [#devops](https://hashnode.com/tag/devops)
-   [#version-control](https://hashnode.com/tag/version-control)
-   [#developer-tools](https://hashnode.com/tag/developer-tools)
-   [#productivity](https://hashnode.com/tag/productivity)

## Written by

[Amaresh Pelleti](https://hashnode.com/@amareswer)

@amareswer

  
[View profile](https://hashnode.com/@amareswer)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
