{"id":13503260,"url":"https://github.com/michaeldfallen/git-radar","last_synced_at":"2026-01-22T13:33:51.116Z","repository":{"id":26921355,"uuid":"30383524","full_name":"michaeldfallen/git-radar","owner":"michaeldfallen","description":"A heads up display for git","archived":false,"fork":false,"pushed_at":"2020-08-31T20:06:45.000Z","size":452,"stargazers_count":2592,"open_issues_count":34,"forks_count":85,"subscribers_count":42,"default_branch":"master","last_synced_at":"2024-10-31T23:30:53.795Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/michaeldfallen.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-02-05T23:07:48.000Z","updated_at":"2024-10-20T16:04:21.000Z","dependencies_parsed_at":"2022-07-12T16:08:57.582Z","dependency_job_id":null,"html_url":"https://github.com/michaeldfallen/git-radar","commit_stats":null,"previous_names":[],"tags_count":8,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/michaeldfallen%2Fgit-radar","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/michaeldfallen%2Fgit-radar/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/michaeldfallen%2Fgit-radar/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/michaeldfallen%2Fgit-radar/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/michaeldfallen","download_url":"https://codeload.github.com/michaeldfallen/git-radar/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":246196915,"owners_count":20739193,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-07-31T22:02:43.844Z","updated_at":"2026-01-22T13:33:51.072Z","avatar_url":"https://github.com/michaeldfallen.png","language":"Shell","readme":"# Git Radar\n\nA heads up display for git.\n\n![An example of git-radar]\n\nGit-radar is a tool you can add to your prompt to provide at-a-glance\ninformation on your git repo. It's a labour of love I've been dogfooding for the\nlast few years. Maybe it can help you too.\n\n**Table of Contents**\n\n- [Installation](#installation)\n- [Usage](#usage)\n- [Features](#features)\n  - [Files status](#files-status)\n  - [Local commits status](#local-commits-status)\n  - [Remote commits status](#remote-commits-status)\n  - [Stash status](#stash-status)\n  - [(Optional) Auto-fetch repos](#optional-auto-fetch-repos)\n- [Customise your prompt](#customise-your-prompt)\n- [Support](#support)\n  - [Ensuring prompt execution](#ensuring-prompt-execution)\n  - [Configuring colours](#configuring-colours)\n    - [Exporting Environment Variables](#exporting-environment-variables)\n    - [Setting an RC file](#setting-an-rc-file)\n    - [Bash Colour Codes](#bash-colour-codes)\n    - [Zsh Colour Codes](#zsh-colour-codes)\n    - [Configuration values](#configuration-values)\n      - [Colouring the Branch part](#colouring-the-branch-part)\n      - [Colouring the local commits status](#colouring-the-local-commits-status)\n      - [Colouring the remote commits status](#colouring-the-remote-commits-status)\n      - [Colouring the file changes status](#colouring-the-file-changes-status)\n- [License](#license)\n- [Links](#links)\n\n## Installation\n\n### Install from brew:\n\n```\n\u003e brew install michaeldfallen/formula/git-radar\n```\n\n### Manually:\n\n```\n\u003e cd ~ \u0026\u0026 git clone https://github.com/michaeldfallen/git-radar .git-radar\n\u003e echo 'export PATH=$PATH:$HOME/.git-radar' \u003e\u003e ~/.bashrc\n```\n\nThen run `git-radar` to see the docs and prove it's installed.\n\n## Usage\n\nTo use git-radar you need to add it to your prompt. This is done in different\nways depending on your shell.\n\n**Bash**\n\nAdd to your `.bashrc`\n```bash\nexport PS1=\"$PS1\\$(git-radar --bash --fetch)\"\n```\n[(note: the `\\` escaping the `$` is important)](#ensuring-prompt-execution)\n\n**Zsh**\n\nAdd to your `.zshrc`\n```zsh\nexport PROMPT=\"$PROMPT\\$(git-radar --zsh --fetch) \"\n```\n[(note: the `\\` escaping the `$` is important)](#ensuring-prompt-execution)\n\n**Fish**\n\nAdd to your `config.fish`\n```bash\nfunction fish_prompt\n    set_color $fish_color_cwd\n    echo -n (prompt_pwd)\n    echo -n (git-radar --fish --fetch)\n    set_color normal\n    echo -n ' \u003e '\nend\n```\n\n## Features\n\n### Files status\n\nThe prompt lists the file changes and whether they are staged, unstaged or\nuntracked.\n\nPrompt                     | Meaning\n---------------------------|--------\n![git:(master) 3A]         | We have 3 untracked files\n![git:(master) 2D2M]       | We have 2 modifications and 2 deletions not yet staged to commit\n![git:(master) 1M1R]       | We have 1 modification and a file renamed staged and ready to commit\n![git:(master) 1U]         | We have a conflict caused by US that we need to address\n![git:(master) 1M 1D2M 2A] | A combination of the above types\n\nEach symbol represents a different change to a file. These are based on what git\nconsiders has happened to the file.\n\nSymbol  | Meaning\n--------|--------\nA       | A new Added file\nD       | A file has been Deleted\nM       | A file has been Modified\nR       | A file has been renamed\nC       | A file has been copied\nU       | A conflict caused by Us\nT       | A conflict caused by Them\nB       | A conflict caused by Both us and them\n\nThe color tells you what stage the change is at.\n\nColor   | Meaning\n--------|--------\nGreen   | Staged and ready to be committed (i.e. you have done a `git add`)\nRed     | Unstaged, you'll need to `git add` them before you can commit\nGrey    | Untracked, these are new files git is unaware of\nYellow  | Conflicted, these need resolved before they can be committed\n\nThe use of feature is controlled by the `GIT_RADAR_FORMAT` environment variable.\nSee [Customise your prompt](#customise-your-prompt) for how to personalise this.\n\n### Local commits status\n\nThe prompt will show you the difference in commits between your branch and the\nremote your branch is tracking. The examples below assume you are checked out on\n`master` and are tracking `origin/master`.\n\nPrompt              | Meaning\n--------------------|--------\n![git:(master 2↑)]  | We have 2 commits to push up\n![git:(master 3↓)]  | We have 3 commits to pull down\n![git:(master 3⇵5)] | Our version and origins version of `master` have diverged\n\nThe use of feature is controlled by the `GIT_RADAR_FORMAT` environment variable.\nSee [Customise your prompt](#customise-your-prompt) for how to personalise this.\n\n### Remote commits status\n\nThe prompt will also show the difference between your branch on origin and what\nis on `origin/master`. This a is hard coded branch name which I intend to make\nconfigurable in the future.\n\nThis is the difference between the commits you've pushed up and `origin/master`.\n\nPrompt                     | Meaning\n---------------------------|---------------\n![git:(m ← 2 my-branch)]   | We have 2 commits on `origin/my-branch` that aren't on `origin/master`\n![git:(m 4 → my-branch)]   | There are 4 commits on `origin/master` that aren't on `origin/my-branch`\n![git:(m 1 ⇄ 2 my-branch)] | `origin/master` and `origin/my-branch` have diverged, we'll need to rebase or merge\n\nThe use of feature is controlled by the `GIT_RADAR_FORMAT` environment variable.\nSee [Customise your prompt](#customise-your-prompt) for how to personalise this.\n\n### Stash status\nThe prompt will show you whether and how many stashes you have stored.\n\nPrompt                     | Meaning\n---------------------------|---------------\n![git:(master) 1≡]         | We have one stash\n\nIf you don't rely on this status, you can always hide this part of the prompt by\n[customising your prompt](#customise-your-prompt)\n\n### (Optional) Auto-fetch repos\n\nEnsuring your refs are up to date I found can be a pain. To streamline this\ngit-radar can be configured to auto-fetch your repo. When the `--fetch` flag is\nused git-radar will run `git fetch` asynchronously every 5 minutes.\n\nThis will only occur when the prompt is rendered and it will only occur on the\nrepo you are currently in.\n\nTo use this feature, when setting your prompt, call git-radar with `--fetch`:\n\n**Bash**\n```bash\nexport PS1=\"$PS1\\$(git-radar --bash --fetch)\"\n```\n[(note: the `\\` escaping the `$` is important)](#ensuring-prompt-execution)\n\n**Zsh**\n```zsh\nexport PROMPT=\"$PROMPT\\$(git-radar --zsh --fetch) \"\n```\n[(note: the `\\` escaping the `$` is important)](#ensuring-prompt-execution)\n\nYou may also choose to fetch at a customized interval of time. To do so, add\nthis to your .bashrc, .zshrc:\n\n```bash\nexport GIT_RADAR_FETCH_TIME=\u003cseconds\u003e\n```\n\nFor example, to fetch every 30 seconds (instead of the default 5 minutes):\n\n```bash\nexport GIT_RADAR_FETCH_TIME=30\n```\n\nYou can also do this in the gitradarrc file:\n\n```bash\nGIT_RADAR_FETCH_TIME=30\n```\n\n## Customise your prompt\n\nGit Radar is highly customisable using a prompt format string. The 4 features\nabove: remote commits, local commits, branch and file changes; are controlled\nby the prompt format string.\n\nFeature        | Control string\n---------------|---------------\nRemote commits | `%{remote}`\nLocal commits  | `%{local}`\nBranch         | `%{branch}`\nFile changes   | `%{changes}`\nStashes        | `%{stash}`\n\nYou can create any prompt shape you prefer by exporting `GIT_RADAR_FORMAT` with\nyour preferred shape. The control strings above will be replaced with the output\nof the corresponding feature.\n\n**Examples**\n\nGIT_RADAR_FORMAT                      | Result\n--------------------------------------|---------------------\n`%{branch}%{local}%{changes}`         | `master1↑1M`\n`[%{branch}] - %{local} - %{changes}` | `[master] - 1↑ - 1M`\n\n### Prefixing and Suffixing the features\n\nOften you will want certain parts of the prompt to only appear when there is\ncontent to render. For example, when in a repo you want `[branch]` but when out\nof a repo you don't want the `[]` appearing.\n\nTo do this the control strings support prefixes and suffixes. Prefixes and\nSuffixes are separated from the feature name by `:` and will only render if the\nfeature would render:\n\nFormat: `prompt \u003e %{prefix - :changes: - suffix}`\n\nIn a repo: `prompt \u003e prefix - 1M - suffix`\n\nOutside a repo: `prompt \u003e `\n\nThe default prompt format uses this to add spaces only if the feature would\nrender. In that way the prompt always looks well spaced out no matter how many\nfeatures are rendering.\n\n\n## Support\n\n### Ensuring prompt execution\n\nWhen setting your prompt variable, `PROMPT` in Zsh and `PS1` in Bash, it's\nimportant that the function executes each time the prompt renders. That way the\nprompt will respond to changes in your git repo. To ensure this you will need\nto escape the execution of the function. There are two ways to do this:\n\n**1. Use `$'` to render raw characters**\n```bash\nexport PROMPT=$'$(git-radar --zsh)'\nexport PS1=$'$(git-radar --bash)'\n```\n\n**2. Use `\\` to escape execution of the subshell**\n```bash\nexport PROMPT=\"\\$(git-radar --zsh)\"\nexport PS1=\"\\$(git-radar --bash)\"\n```\n\n### Configuring colours\n\nYou can configure the colour scheme in two ways: export\n[Environment Variables](#exporting-environment-variables)\nor use an [rc file](#setting-an-rc-file).\n\n#### Exporting Environment Variables\n\nTo configure the prompt this way just add to your `~/.bashrc` or `~/.zshrc` an\nexport directive with the value you want to change.\n\n**Example: Change the branch colour in Zsh**\n\nIn `~/.zshrc`:\n```zsh\nexport GIT_RADAR_COLOR_BRANCH='$fg[yellow]'\n```\n\n**Example: Change the branch colour in Bash**\n\nIn `~/.bashrc`:\n```zsh\nexport GIT_RADAR_COLOR_BRANCH='\\\\033[0;33m'\n```\n\n#### Setting an RC file\n\nGit radar supports multiple rc files. One of these will be sourced when the\nprompt renders.\n\n**Example: Change the branch colour in Zsh**\n\nIn `~/.gitradarrc`:\n```zsh\nGIT_RADAR_COLOR_BRANCH='$fg[yellow]'\n```\n\n**Basic RC file**\n\nCreate a file at `~/.gitradarrc` which sets the Environment variables listed in\n[Configuration values](#configuration-values) using colour codes listed in\neither [Zsh Colour Codes](#zsh-colour-codes) or\n[Bash Colour Codes](#Bash-Colour-Codes) depending on your shell.\n\n**Shell specific RC file**\n\nIf you use both Bash and Zsh you can set RC files that are specific for those\nshells.\n\nFor Bash: Create a file at `~/.gitradarrc.bash`\n\nFor Zsh: Create a file at `~/.gitradarrc.zsh`\n\n\n#### Bash Colour Codes\n\nBash colour codes make use of the colours your terminal app claims to be `red`\nor `green`. Using one of these codes will only produce the colour your terminal\nclaims, so you should customise your colour scheme on your terminal as well as\ncustomising git-radar.\n\nNote the \"Bright\" colours can be shown as bold instead, it depends on your\nterminal. By default, for example, the Mac OSX Terminal.app uses the \"Bright\"\ncolours to provide 8 new lighter colours but some terminals only support 8 and\nwill show the text as bold instead.\n\nColour        | Code for Text  | Code for Background\n--------------|----------------|--------------------\nBlack         | `\\\\033[0;30m`  | `\\\\033[0;40m`\nRed           | `\\\\033[0;31m`  | `\\\\033[0;41m`\nGreen         | `\\\\033[0;32m`  | `\\\\033[0;42m`\nYellow        | `\\\\033[0;33m`  | `\\\\033[0;43m`\nBlue          | `\\\\033[0;34m`  | `\\\\033[0;44m`\nMagenta       | `\\\\033[0;35m`  | `\\\\033[0;45m`\nCyan          | `\\\\033[0;36m`  | `\\\\033[0;46m`\nWhite         | `\\\\033[0;37m`  | `\\\\033[0;47m`\nBright Black  | `\\\\033[1;30m`  | `\\\\033[1;40m`\nBright Red    | `\\\\033[1;31m`  | `\\\\033[1;41m`\nBright Green  | `\\\\033[1;32m`  | `\\\\033[1;42m`\nBright Yellow | `\\\\033[1;33m`  | `\\\\033[1;43m`\nBright Blue   | `\\\\033[1;34m`  | `\\\\033[1;44m`\nBright Magenta| `\\\\033[1;35m`  | `\\\\033[1;45m`\nBright Cyan   | `\\\\033[1;36m`  | `\\\\033[1;46m`\nBright White  | `\\\\033[1;37m`  | `\\\\033[1;47m`\nReset         | `\\\\033[0m`     | `\\\\033[0m`\n\nNote the Reset will set back to what your terminal claims as standard text and\nbackground.\n\n#### Zsh Colour Codes\n\nZsh also provides a way to access the colours that your terminal claims as `red`\nor `green`, etc.\n\nNote the \"Bright\" colours can be shown as bold instead, it depends on your\nterminal. By default, for example, the Mac OSX Terminal.app uses the \"Bright\"\ncolours to provide 8 new lighter colours but some terminals only support 8 and\nwill show the text as bold instead.\n\nColour        | Code for Text      | Code for Background\n--------------|--------------------|--------------------\nBlack         | `$fg[black]`       | `$bg[black]`\nRed           | `$fg[red]`         | `$bg[red]`\nGreen         | `$fg[green]`       | `$bg[green]`\nYellow        | `$fg[yellow]`      | `$bg[yellow]`\nBlue          | `$fg[blue]`        | `$bg[blue]`\nMagenta       | `$fg[magenta]`     | `$bg[magenta]`\nCyan          | `$fg[cyan]`        | `$bg[cyan]`\nWhite         | `$fg[white]`       | `$bg[white]`\nBright Black  | `$fg_bold[black]`  | `$bg_bold[black]`\nBright Red    | `$fg_bold[red]`    | `$bg_bold[red]`\nBright Green  | `$fg_bold[green]`  | `$bg_bold[green]`\nBright Yellow | `$fg_bold[yellow]` | `$bg_bold[yellow]`\nBright Blue   | `$fg_bold[blue]`   | `$bg_bold[blue]`\nBright Magenta| `$fg_bold[magenta]`| `$bg_bold[magenta]`\nBright Cyan   | `$fg_bold[cyan]`   | `$bg_bold[cyan]`\nBright White  | `$fg_bold[white]`  | `$bg_bold[white]`\nReset         | `$reset_color`     | `$reset_color`\n\n#### Configuration values\n\nAll these values should be set using a the correct colour code for your\nterminal. You should also choose the colour code based on what shell you are\nusing. There is a way to support [colouring multiple shells using rc files](#setting-an-rc-file).\n\n##### Colouring the Branch part\n\n**GIT_RADAR_COLOR_BRANCH='[colour code]'**\n```\ngit:(my-branch)\n     ^^^^^^^^^\n```\nThe colour to use for the Branch or git reference.\n\nIt is unset by\n`GIT_RADAR_COLOR_BRANCH_RESET` which you can set if you want a different\nbackground colour to return to.\n\n##### Colouring the local commits status\n\n**GIT_RADAR_COLOR_LOCAL_AHEAD='[colour code]'**\n```\ngit:(my-branch 1↑)\n                ^\n```\nThe colour to use for the arrow that indicates how many commits you have to push\nup.\n\nIt is unset by `GIT_RADAR_COLOR_LOCAL_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_LOCAL_BEHIND='[colour code]'**\n```\ngit:(my-branch 1↓)\n                ^\n```\nThe colour to use for the arrow that indicates how many commits you have to pull\ndown.\n\nIt is unset by `GIT_RADAR_COLOR_LOCAL_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_LOCAL_DIVERGED='[colour code]'**\n```\ngit:(my-branch 1⇵1)\n                ^\n```\nThe colour to use for the arrow that indicates how many commits your branch has diverged by.\n\nIt is unset by `GIT_RADAR_COLOR_LOCAL_RESET` which you can set if you want\na different background colour to return to.\n\n##### Colouring the remote commits status\n\n**GIT_RADAR_COLOR_REMOTE_AHEAD='[colour code]'**\n```\ngit:(m ← 1 my-branch)\n       ^\n```\nThe colour to use for the arrow that indicates how many commits your branch has to merge on to master.\n\nIt is unset by `GIT_RADAR_COLOR_REMOTE_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_REMOTE_BEHIND='[colour code]'**\n```\ngit:(m 1 → my-branch)\n         ^\n```\nThe colour to use for the arrow that indicates how many commits your branch is\nbehind master.\n\nIt is unset by `GIT_RADAR_COLOR_REMOTE_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_REMOTE_DIVERGED='[colour code]'**\n```\ngit:(m 1 ⇄ 1 my-branch)\n         ^\n```\nThe colour to use for the arrow that indicates how many commits your branch has\ndiverged from master.\n\nIt is unset by `GIT_RADAR_COLOR_REMOTE_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_REMOTE_NOT_UPSTREAM='[colour code]'**\n```\ngit:(upstream ⚡ my-branch)\n              ^\n```\nThe colour to use for the lightning bolt which indicates that your branch is not\ntracking an upstream branch.\n\nIt is unset by `GIT_RADAR_COLOR_REMOTE_RESET` which you can set if you want\na different background colour to return to.\n\n##### Colouring the file changes status\n\n**GIT_RADAR_COLOR_CHANGES_STAGED='[colour code]'**\n```\ngit:(my-branch) 1M\n                 ^\n```\nThe colour to use for the letters that indicate changes that have been staged to\ncommit.\n\nIt is unset by `GIT_RADAR_COLOR_CHANGES_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_CHANGES_UNSTAGED='[colour code]'**\n```\ngit:(my-branch) 1M\n                 ^\n```\nThe colour to use for the letters that indicate changes that have not yet been\nstaged to commit.\n\nIt is unset by `GIT_RADAR_COLOR_CHANGES_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_CHANGES_CONFLICTED='[colour code]'**\n```\ngit:(my-branch) 1B\n                 ^\n```\nThe colour to use for the letters that indicate changes that have conflicts that\nneed resolved.\n\nIt is unset by `GIT_RADAR_COLOR_CHANGES_RESET` which you can set if you want\na different background colour to return to.\n\n**GIT_RADAR_COLOR_CHANGES_UNTRACKED='[colour code]'**\n```\ngit:(my-branch) 1A\n                 ^\n```\nThe colour to use for the letters that indicate files that are currently not\ntracked by git.\n\nIt is unset by `GIT_RADAR_COLOR_CHANGES_RESET` which you can set if you want\na different background colour to return to.\n\n##### Colouring the stash status\n\n**GIT_RADAR_COLOR_STASH='[colour code]'**\n```\ngit:(my-branch) 1≡\n                 ^\n```\nThe colour to use for the lines that indicates how many stashes you have stored.\n\nIt is unset by `GIT_RADAR_COLOR_STASH_RESET` which you can set if you want\na different background colour to return to.\n\n## License\n\nGit Radar is licensed under the MIT license.\n\nSee [LICENSE] for the full license text.\n\n## Links\n\n* [mini-git-radar](https://github.com/bogem/mini-git-radar) - lightweight version of git-radar. Only for macOS and bash/fish.\n\n[LICENSE]: https://github.com/michaeldfallen/git-radar/blob/master/LICENSE\n[git:(master) 1≡]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/stash.png\n[git:(master) 3A]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/untracked.png\n[git:(master) 2D2M]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/unstaged.png\n[git:(master) 1M1R]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/added.png\n[git:(master) 1U]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/conflicts.png\n[git:(master) 1M 1D2M 2A]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/combination.png\n[git:(master 2↑)]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/local%20is%20ahead.png\n[git:(master 3↓)]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/remote%20is%20behind.png\n[git:(master 3⇵5)]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/remote%20local%20diverged.png\n[git:(m ← 2 my-branch)]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/branch%20is%20ahead.png\n[git:(m 4 → my-branch)]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/master%20is%20ahead.png\n[git:(m 1 ⇄ 2 my-branch)]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/master%20branch%20diverged.png\n[An example of git-radar]: https://raw.githubusercontent.com/michaeldfallen/git-radar/master/images/detailed.png\n","funding_links":[],"categories":["Shell","Shells","Dev"],"sub_categories":["Git"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmichaeldfallen%2Fgit-radar","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmichaeldfallen%2Fgit-radar","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmichaeldfallen%2Fgit-radar/lists"}