dsh-workspace-git-badge

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-01），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

# dsh-git-badge

Git status badges for [DeepSeek Harness](https://github.com/deepseek-ai/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`](docs/badge-explainer.md)
for a beginner-friendly walkthrough.

## Install

```bash
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](https://github.com/deepseek-ai/deepseek-harness/discussions/5092)).

From a clone of this repo:

```bash
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`](SEAM.md) / [`PR.md`](PR.md).

## Testing

See [`TESTING.md`](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](LICENSE)