Back to home@Kevin-McIsaac

dsh-workspace-git-badge

No description

Stars
0
Language
JavaScript
Created
Aug 30, 2026
Updated
Sep 3, 2026
GitHub repo

Introduction

dsh-git-badge

Git status badges for DeepSeek Harness

🟡 main ↑0 ↓2 ✎3

What you get

The Git status badge for a project in the:

  • input box after the access picker. image
  • workspace after each project name. (May require the seam patch to enable)
    Project 1   | 🟡 main
    Project 2   | 🟢 main
    
Git status is updated within seconds of any commit, checkout, stage, or file edit.

Dot colors

The dot encodes a three-state summary (checked top-down, first match wins):

DotWhenWhat to do
🔴 redUnmerged files (merge/rebase conflict in progress), or a dirty tree that is also behind upstreamResolve conflicts, or commit your edits before pulling
🟡 yellowDirty files, or any ahead/behind (sync pending)Commit (✎), push (↑), or pull (↓) when convenient
🟢 greenClean and in sync with the upstreamNothing

Red never means merely "behind" — a clean tree one commit behind is a normal between-pulls state. See docs/badge-explainer.md for a beginner-friendly walkthrough.

Install

dsh plugin --profile web add dsh-git-badge

Then restart the web process and refresh the browser. This will activate the input status chip.

Sidebar row badges need the proposed new workspace seam. If this is not available apply the patch (discussion #5092).

From a clone of this repo:

seam/apply.sh apply     # patch the installed DSH (hash-guarded), then restart dsh web
seam/apply.sh revert    # restore pristine at any time

Notes:

  • The patch lives in node_modules, so a DSH reinstall/update reverts it — re-run seam/apply.sh apply afterwards.
  • The hash-guard refuses to patch if the installed file doesn't match the pinned upstream build (it never blind-overwrites an update). Rebuild the patch with seam/make-patch.sh + seam/stamp-hash.sh after a DSH release changes the file.
  • Once upstream ships the seam itself, apply becomes a no-op and the npm-installed plugin picks it up with no changes on your side.

Details, safety rails, and the upstream proposal are in SEAM.md / PR.md.

Testing

See TESTING.md — clean-profile boot (customer simulation), seam apply/revert procedure, and the gotchas list.

Requirements

  • Node.js ≥ 20, git on PATH
  • DSH with the web profile (any install)

License

MIT