![]() ![]() | `?42` | this many untracked files | `git status -ignore-submodules=dirty` | | `!42` | this many unstaged changes | `git status -ignore-submodules=dirty` | | `+42` | this many staged changes | `git status -ignore-submodules=dirty` | | `~42` | this many merge conflicts | `git status -ignore-submodules=dirty` | | `merge` | repository state | `git status -ignore-submodules=dirty` | | `*42` | this many stashes | `git stash list` | | `⇢42` | this many commits ahead of the push remote | `git rev-list -left-right -count | | `⇠42` | this many commits behind the push remote | `git rev-list -left-right -count | | `⇡42` | this many commits ahead of the remote | `git status -ignore-submodules=dirty` | | `⇣42` | this many commits behind the remote | `git status -ignore-submodules=dirty` | | `master` | remote tracking branch only shown if different from local branch | `git rev-parse -abbrev-ref -symbolic-full-name | | `feature` | current branch replaced with `#tag` or if not on a branch | `git status -ignore-submodules=dirty` | When using Lean, Classic or Rainbow style, Git status may look like this: feature:master ⇣42⇡42 ⇠42⇢42 *42 merge ~42 +42 !42 ?42 Super stoked about speaking at #KubeCon EU in May □įrom Monitoring to Observability: Left Shift your SLOs with ChaosĬome and say hi, in person □ #o11ylove : What do different symbols in Git status mean? One step further to my KubeCon EU talk in May 2022 :-) You can find the full configuration in my dotfiles project.Ī clear terminal representation is helpful for workshops and live demos during talks, allowing participants to follow more easily. Also, when the command returned an error which is reflected with printing the exit code.Ĭommands can also take a while to execute (or to study the git diff output), which is represented with the 10s and 4s yellow text in the screenshot. If there are uncommitted changes, the prompt looks different.
0 Comments
Leave a Reply. |