The Bad Deploy — Gitor

📁 Files

No files yet. Create one!

! ConflictS StagedM ModifiedU Untracked

No files staged. Use git add to stage changes.

📊 Commit Graphcurrent branchmain

🏷️ TaggingBeginner0/5

📖 Concepts

TagA named reference to a specific commit. Unlike branches, tags do not move when new commits are made. Used for marking important points in history — typically releases (v1.0, v2.0).

Lightweight TagJust a name pointing to a commit (like a branch that never moves). No extra metadata.

Annotated TagA tag with metadata: author, date, and message. Stored as a full Git object. Created with git tag -a.

View commit history to find the release commit

Look at the log to see which commit should be tagged as a release.

● View commit history to find the release commit

○ Create a tag at the initial commit

○ Tag the current HEAD as "v1.0"

○ List all tags

○ Delete the "v0.1" tag

🧩 The Bad DeployUnsolved

📖 Story

Commit mmmm2222 "Enable dark mode by default" just broke production — turns out it had a CSS bug that made text invisible. The branch has already been pushed and your teammates have pulled. You cannot rewrite history with reset — that would break everyone's repos. Safely undo the bad commit by creating a new commit that reverses its changes, leaving history intact.

Goal

Solve the problem by using the correct Git commands.

Terminal

🧩 Problem: The Bad Deploy

A commit broke production. Revert it safely without rewriting shared history.

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