dsh-workspace-git-badge
界面增强 活跃维护

dsh-workspace-git-badge

Kevin-McIsaac/dsh-workspace-git-badge

为Git仓库生成简洁的状态徽章,直观展示当前分支的提交增减、未提交修改文件数量,配置简单可直接嵌入项目README,无需额外依赖即可快速呈现仓库活跃状态。

0
Stars 标星
0
Forks 分支
0
Watchers 关注
0
Open Issues
JavaScript
主要语言
MIT
开源协议
127 KB
仓库大小
23 天前
最后推送
一键安装扩展 / 插件指令
dsh plugin --profile web add github:Kevin-McIsaac/dsh-workspace-git-badge
git clone https://github.com/Kevin-McIsaac/dsh-workspace-git-badge.git
git clone git@github.com:Kevin-McIsaac/dsh-workspace-git-badge.git
README.md main

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):

Dot When What to do
🔴 red Unmerged files (merge/rebase conflict in progress), or a dirty tree that is also behind upstream Resolve conflicts, or commit your edits before pulling
🟡 yellow Dirty files, or any ahead/behind (sync pending) Commit (✎), push (↑), or pull (↓) when convenient
🟢 green Clean and in sync with the upstream Nothing

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