codipry.

Keyboard shortcuts

Use Ctrl on Windows/Linux or Command on macOS. Shortcuts respect focused text fields.

Ctrl/⌘ K
Open or close tool search
?
Open this reference outside text inputs
Escape
Close the active dialog
Ctrl/⌘ S
Save the current Playground project
Ctrl/⌘ Enter
Run the Playground preview
Tab
Move between controls; inside code typing, insert two spaces
Shift Tab
Move to the previous control

Monaco also provides its own command palette. Browser and operating-system shortcuts can take priority.

Start creating
Frontend PlaygroundcodeResponsive LabcodeGradient GeneratordesignBox Shadow GeneratordesignText Shadow GeneratordesignBorder Radius GeneratordesignFlexbox GeneratordesignCSS Grid GeneratordesignAnimation GeneratordesignGlassmorphism GeneratordesignClip Path GeneratordesignFluid Type GeneratordesignColor StudiodesignGit Command BuildergitGit VisualizergitMerge vs. RebasegitSQL Joins VisualizerdatabaseSQL Clause ExplorerdatabaseDatabase RelationshipsdatabaseSQL FormatterdatabaseSQL PlaygrounddatabaseTyping TestpracticeCode Typing TestpracticeJSON FormattercodeCSV / JSON ConvertercodeText DiffcodeRegex TestercodeEncoding ToolscodeHash GeneratorcodeTimestamp ConvertercodeCSS Transform GeneratordesignCSS Filter GeneratordesignDesign Token ExporterdesignGit Conflict TrainergitSQL Schema Explorerdatabase
Your next idea is a few keystrokes away.Esc to close
Tools / Git
Understand before you run

Git Conflict Trainer

Resolve original merge-conflict lessons by choosing, combining or editing both sides.

How to use Git Conflict Trainer

Practice the mechanical and reasoning steps of a merge conflict with original, local text lessons. No repository is opened and no Git command is run.

  1. Read the lesson requirement and inspect our side and their side.
  2. Choose ours, theirs, both or a manual replacement for the next block.
  3. Check the full result against the requirement, then copy or export it.

A practical starting point

When two branches add independent list items, preserving both can be correct. When they change the same setting, choose the value that meets the review requirement.

<<<<<<< ours
- Local drafts
=======
- Portable exports
>>>>>>> theirs

Common mistakes

  • Removing markers does not establish that the content is correct.
  • Accepting both can duplicate definitions or break syntax.
  • Ours/theirs labels have different interpretations during a real rebase.

Frequently asked questions

Does the trainer modify my repository?

No. It edits browser-local lesson text only.

Is this a general merge engine?

No. It supports bounded two-sided marker blocks for teaching; nested and diff3 base markers are rejected.