Dev & Ops

Git & version control tools

Git gets risky exactly at the commands you use least often: a rebase, a force push, or a cherry-pick across branches you don't fully picture in your head. This page has a command builder that explains and warns before you run anything, a graph simulator for previewing merge and rebase outcomes, plus everyday helpers for commit messages, diffs, .gitignore rules and branch name validation.

Reach for the Git simulator specifically when you want to see how a merge, rebase or cherry-pick changes a sample commit graph before trying it on your real repository, and the Git command builder when you know the operation but want the exact flags with an explanation of what each one risks. The gitignore tester traces which rule in your file actually matches a given path, which is faster than guessing from trial and error. Everything here processes the text or repository state you provide locally.

9 tools

Build and preview Git commands

Write commits and validate refs

Manage repo files and links

Git & Version Control tools FAQ

How can I see what a rebase will do before actually running it?

The Git simulator lets you set up a sample commit graph and preview how a merge, rebase or cherry-pick would rearrange it, without touching a real repository. It's a safer way to build intuition for history-rewriting commands before running them on branches other people depend on.

Why isn't a file being ignored even though it's listed in .gitignore?

A later rule can re-include a path an earlier rule excluded, and patterns are evaluated in file order with directory-specific rules taking precedence. The gitignore tester traces exactly which rule matches a given path and explains the decision chain, faster than editing the file and testing with git status.

What is a Conventional Commit and why do teams enforce it?

A Conventional Commit prefixes the message with a type like feat, fix or chore and an optional scope, which lets tooling generate changelogs and determine version bumps automatically. The Conventional Commit Builder composes and validates that format, including footers for breaking changes, before you commit.