Choose merge or rebase using branch ownership, publication state and history goals.
Answer a short set of repository-state questions and receive a rule-based recommendation with the relevant command pattern and caution.
Rebase is often useful for your own unpublished branch when you want a clean sequence before integration. It rewrites commit IDs, so shared history requires extra care.
Merge is safer when the branch is already shared or when preserving the exact topology of collaboration matters more than a linear history.
Do not rebase commits that teammates are already depending on unless the team explicitly coordinates the history rewrite.
Answer a short set of repository-state questions and receive a rule-based recommendation with the relevant command pattern and caution.
Use the input area to paste text or upload an existing file, then process it and inspect the generated result, warnings and statistics.
Use the supplied sample first, then replace it with a real repository export, configuration file, branch list or measurement report appropriate to this tool.