SOH4C4759/dsh-plugin-cicd ↗★ 0
dsh-plugin-cicd
发布台（Release Console）for DeepSeek Harness: a sidebar entry and a full main-panel page that show what each repository has built, what it has released, whether the local checkout is ahead of the release, whether the copy installed in this profile is the published artifact, and which version npm holds — with buttons to trigger a build, cut a release, publish a draft, push that version to npm, install the release into the profile, and hand a restart to dsh-plugin-restart. It also carries the third channel: when a repository's release goes public, one short update note is posted under the video that introduces the plugin, with the credential obtained from a Bilibili sign-in inside the panel. Reuses the machine's authenticated gh CLI and the Host's own package manager, so the plugin stores no GitHub or npm credential of its own; the one credential it does own is the Bilibili session it created, kept in its own directory and never echoed back. 适合需要监控多个仓库发布状态、对比本地检出并一键更新插件的开发者。
インストール
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:SOH4C4759/dsh-plugin-cicdドキュメント
README 全文を読む ↗配置：用脚本，不要手改 YAML
包本身不带仓库列表——哪些仓库被监视是部署状态，不是包状态；把某个人的私有仓库名打进公开包，每个安装者都得先去拆它。
列表放在一个由脚本管理的 JSON 文件里（默认 %USERPROFILE%\.dsh\dsh-plugin-cicd\repos.json），profile patch 只留两行机器相关的配置：
- id: dsh-plugin-cicd
config:
owner: SOH4C4759
ghPath: 'C:\Program Files\GitHub CLI\gh.exe'
日常操作全走插件自带的脚本：
$cfg = "$env:USERPROFILE\.dsh\profiles\desktop\node_modules\dsh-plugin-cicd\scripts\configure.mjs"
## 首次使用：授权引导
面板不自己存凭据，它用你机器上的 `gh`。所以第一次打开时它可能无事可做——这时面板不会只显示一句"读不到"，而是**按缺什么给什么**：
| 状态 | 面板给出 |
|---|---|
| 找不到 `gh` | `winget install --id GitHub.cli`（可一键复制）+ cli.github.com 链接 |
| 装了但没登录 | `gh auth login`，并说明选 GitHub.com → HTTPS → 浏览器登录，完成后点「重新检测」 |
| 登录了但缺 scope | `gh auth refresh -h github.com -s repo,workflow`，缺哪个补哪个 |
| 没有任何仓库 | `configure.mjs add ...` 的实际命令 + 配置文件路径 |
scope 是从 `gh auth status` 真读出来的：缺 `repo` 读不到私有仓库，缺 `workflow` 无法触发构建——这两种情况在按钮按下去之前就会说明白。细粒度 token 不报 scope 行时按"未知"处理，不会误报成"全都缺"。