The Sneaky Regression — Gitor

📁 Files

No files yet. Create one!

! ConflictS StagedM ModifiedU Untracked

No files staged. Use git add to stage changes.

📊 Commit Graphcurrent branchmain

↩️ Oops! Undoing ChangesIntermediate0/5

📖 Concepts

RevertCreates a NEW commit that undoes the changes from a previous commit. Safe for shared history — it doesn't rewrite the past.

Reset (--soft)Moves the branch pointer backward but keeps changes in the staging area. The working directory stays untouched.

Reset (--mixed)Moves the branch pointer and unstages changes. This is the default mode. Changes remain in your working directory.

Reset (--hard)Moves the branch pointer, unstages changes, AND resets the working directory. Destructive — uncommitted changes are lost.

View the commit history

Notice the latest commit "Oops bad commit" is the last entry. We want to undo it.

● View the commit history

○ Revert the bad commit

○ Reset to remove the last 2 commits (soft)

○ Reset mixed (default)

○ Reset hard — discard everything

🧩 The Sneaky RegressionUnsolved

📖 Story

Something broke the calculateTotal function sometime in the last week. It used to return a number, now it returns undefined. You know commit 00000000 was good. The current HEAD is bad. Use git bisect to efficiently find which commit introduced the bug. There are 5 commits to check — bisect will find it in at most 3 steps. The bug is in the commit that changed src/calc.js to remove the return statement.

Goal

Solve the problem by using the correct Git commands.

Terminal

🧩 Problem: The Sneaky Regression

A bug was introduced somewhere in the last 5 commits. Use git bisect to find the exact commit that broke things.

Use the terminal to solve the problem. Results are checked automatically.