Git Rebase Playground
Step through fork detection, commit replay, new commit IDs, and branch pointer movement, then compare the same history with merge.
Git Rebase Playground
Step through fork detection, commit replay, new commit IDs, and branch pointer movement, then compare the same history with merge.
About the Git rebase teaching model
Rebase replays commits on a new base
The model finds the fork point, selects feature commits not on main, recreates them in order with new parents and IDs, and finally moves the feature pointer. Main does not move.
Topology only, not a complete Git repository
The playground does not model files, patches, the index, conflicts, reflog, or garbage collection. Commit IDs are stable six-character teaching labels, not real hashes.
FAQ
Common questions and answers about this topic.
How do I use the Git Rebase Playground?
Choose a scenario, optionally add or remove commits at the main and feature tips, then start rebase. Use Previous, Play, and Next to inspect every immutable step.
Why do commit IDs change after rebase?
A commit identifies its content, metadata, and parent relationship. Replaying it on a different parent creates a different commit even when the patch is similar.
Does this tool run Git or change my repository?
No. The entire graph is a browser-only teaching model. The copied command is plain text and is never executed.