Playground
A make believe working directory on the left, a terminal in the middle, and what mgit decided on the right. All of it lives in this tab and none of it can reach the files on your machine.
Working directory
Sandbox terminal — everything happens in this tab
This terminal needs JavaScript. Nothing else on the site does: the install commands, the option tables and every documentation page work without it.
~/work $
Enter runTab complete↑ ↓ historyCtrl+C interruptCtrl+L clear
What it did
Run an mgit command and this panel lists every directory it opened, every git call it made, and how those results became one exit code.
How real is this?
- Argument parsing, repository discovery, the output format and the exit codes are ported rule by rule from mgit's Rust source, and a parity test keeps them honest: the same working directory and the same command are given to the compiled binary and to this code, and the output has to match character for character.
- git itself is simulated. The sandbox knows what
status,pull,fetch,log,branchandcheckoutshould answer for these make believe repositories. For a git command it does not model, it says so instead of inventing output. - Sandbox paths are always POSIX style. Switching to a Windows output target changes the glyph and colour decisions, not the path format.