k0ndrateff/dsh-plugins

gitlab

在侧栏面板里通过 GitLab REST API 与个人访问令牌查看合并请求、评审讨论串与流水线作业日志,并可评论、回复、解决讨论与批准;写操作均需二次确认(读需 read_api,写需 api)。

Git 与代码评审atlassiandeepseek-harnessfigma

dsh-gitlab-plugin

Merge requests, review threads and pipelines inside DeepSeek Harness, over GitLab's REST API with a personal access token.

Part of DeepSeek Harness Plugins by @k0ndrateff — Jira, Confluence, Sentry, GitLab and Figma integrations for DeepSeek Harness, plus a digest, a cross-provider correlation and project checks built on top of them. Everything is in the market index and listed in the collection README.

Why REST and a token rather than GitLab's MCP server: that server is switched off for a whole top-level group unless an Owner turns it on, and the tokens it issues carry the single scope mcp, which no REST call accepts. A token you already have works everywhere; it is kept in the harness credential store under dsh-gitlab/token. Reads need read_api; the writes below need api.

What you get

  • gitlab_present: merge requests waiting for your review, your own, a search, one

merge request's review findings, or its failed jobs.

  • A merge request panel with four sections — Overview, Diff,

Discussions (filtered to unresolved or to findings, with reply and resolve) and Pipeline (jobs, and a failed job's trace on demand).

  • gitlab_review: comment, reply in a thread, resolve or reopen one, approve or

unapprove. Each of those changes somebody else's merge request, so the tool answers with the exact text it would post until the call carries confirm; the panel shows that draft with a Send button.

  • /gitlab status|login|logout|sync.

Configuration

- id: gitlab
  config:
    endpoint: https://gitlab.com
    debug: false

endpoint is the instance root; calls are made under its /api/v4.