kaziii/dsh-github-connector
DeepSeek Harness (dsh) 的 GitHub 连接器：一键授权，对话内创建/AI 审查/合并 PR | GitHub connector for dsh: one-click connect, create/review/merge PRs from the conversation
Listed
5
Git
Bundle verified
Preview
What it does
GitHub Device Flow connect plus an in-conversation PR workflow: a status bar above the composer for create / AI-review / merge, and github_* tools for search, issue and PR read and write.
Best for
- DSH users who want to authorize GitHub through Device Flow without manually pasting a token in the Web UI.
- Repository workflows that create, AI-review, and merge pull requests from an in-conversation status bar.
- Agents that need GitHub search plus issue and pull-request read/write tools.
Not ideal for
- Non-GitHub repository workflows or conversations with no issue, pull-request, or code-hosting operations.
- Headless setups expecting the Web PR status bar; non-Web profiles can use tools but omit the UI package.
- CLI or headless environments without a `GITHUB_TOKEN` carrying the required repository permissions.
README
dsh-github-connector
| 简体中文 | English |
DeepSeek Harness (dsh) 的 GitHub 连接器插件 —— 一键连接 GitHub 账号，不离开 dsh 对话即可创建 PR、AI 审查 PR、合并 PR。
- 一键连接 —— 在 dsh 设置页走 GitHub Device Flow 授权，无需复制粘贴 token。
- 输入框上方的 PR 状态条 —— 创建 PR / AI 审查 / 合并，由 git 状态触发。
-
模型侧工具 ——
github_search、github_issue_read、github_pr_read、github_issue_create、github_issue_comment、github_pr_create。
检测到当前分支领先默认分支时，输入框上方会出现 PR 状态条，一键创建 PR：
安装
前置条件：Node ≥ 22.19、pnpm、dsh CLI（npm install -g @deepseek-ai/dsh）。
从 npm 一条命令安装：
dsh plugin --profile web add dsh-github dsh-github-rest dsh-tool-github dsh-github-connect dsh-ui-github
（把 web 换成你的 profile 名 —— headless、tui 等。dsh-ui-github 只在 web 客户端渲染，非 web profile 可不装。）
连接 GitHub 账号
打开 dsh 设置 → 插件，点击 连接 GitHub 按钮，按提示完成 Device Flow 授权 —— token 只保存在宿主，不落入任何配置文件：
CLI / headless 场景则设置 GITHUB_TOKEN 环境变量（带 repo 权限的 personal access token）。
许可证
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:kaziii/dsh-github-connector in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.