---
title: "Discussion on \"Use Git Bisect to Find the Commit That Introduced a Bug\" | Hashnode"
description: "Discussion on \"Use Git Bisect to Find the Commit That Introduced a Bug\". As a developer you know that situation: the code worked like a charm and suddenly there is a bug but you have no idea where and when it was introduced.\nIf you are working in a big team the chances may be quite high that many commits have been added i..."
url: "https://hashnode.com/posts/use-git-bisect-to-find-the-commit-that-introduced-a-bug/60e54fe54aacd63048246245"
---

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

Discussion

# [Use Git Bisect to Find the Commit That Introduced a Bug](https://blog.mokkapps.de/use-git-bisect-to-find-the-commit-that-introduced-a-bug?utm_source=hashnode&utm_medium=feed)

As a developer you know that situation: the code worked like a charm and suddenly there is a bug but you have no idea where and when it was introduced. If you are working in a big team the chances may be quite high that many commits have been added i...

Jul 7, 2021 · 4 min read · blog.mokkapps.de  
Read the article

-   [#git](https://hashnode.com/tag/git)
-   [#version-control](https://hashnode.com/tag/version-control)
-   [#bugs-and-errors](https://hashnode.com/tag/bugs-and-errors)

## Written by

[Michael Hoffmann](https://hashnode.com/@mokkapps)

@mokkapps · Munich, Germany

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

💚 I'm helping developers to become Vue experts | 👨🏻‍💻 Senior Frontend Developer | 🌴 Freelancer | ✍️ Blogger |

## Responses 1

Markdown supported · ⌘↵ to post

[Shad Mirza](https://hashnode.com/@iamshadmirza)

[Jul 8, 2021](https://hashnode.com/posts/use-git-bisect-to-find-the-commit-that-introduced-a-bug/60e54fe54aacd63048246245/comment/60e6968ec32fbd1b7372095a)

Today I learned: Git bisect
