Committed to the Wrong Branch — 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

🧩 Committed to the Wrong BranchUnsolved

📖 Story

You were working on a new dashboard feature and forgot to switch branches first. You committed "Add dashboard" directly onto main. Your team's policy: no direct commits to main. The commit needs to be on feature/dashboard instead, and main should be back to where it was. Do this without losing any work.

Goal

Solve the problem by using the correct Git commands.

Terminal

🧩 Problem: Committed to the Wrong Branch

You committed directly to main instead of your feature branch. Move it without losing the work.

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