deepseek-harness/packages/experimental/forge-github

description, kind

description	kind
Serve the experimental forge registry for GitHub hosts through the GitHub CLI on the host.	package-reference

@deepseek-ai/dsh-experimental-forge-github

English | 中文

Summary

Read GitHub and GitHub Enterprise pull requests for ctx.forge with the GitHub CLI that is already signed in on the host. Each poll batches pull requests by host to read state, changed lines, checks, review decision, mergeability, and unresolved review threads for every due pull request.

Table of Contents

• Use this package
• Understand the implementation
• Further Exploration
• Model Experience
• Known Limitations and Deferred Work
• Dev Note

---

Use this package

Mount the provider after the forge registry and list every GitHub Enterprise host explicitly.

- name: '@deepseek-ai/dsh-experimental-forge'
- name: '@deepseek-ai/dsh-experimental-forge-github'
  config:
    hosts: [github.com, ghe.example.com]

The provider runs gh as a host process, even when Sessions execute commands in another execution world. Sign in once per host with gh auth login --hostname <host>. The child receives the host environment without DSH_* variables and without variables whose names contain KEY, PASSWORD, SECRET, or TOKEN, so GH_TOKEN and GITHUB_TOKEN are not forwarded and gh uses its own credential store. Prompts, update notices, pagers, and colors are disabled. maxOutputBytes must be a positive safe integer; only timeoutMs is bounded by the runtime timer limit. ghCommand, hosts, timeoutMs, and maxOutputBytes are listed in the configuration catalog.

The provider serves a remote URL in https, http, ssh, or git form, or in scp form such as [email protected]:owner/name.git, when its host is configured. HTTP(S) remotes retain custom ports in the host identity; SSH and Git transport ports are excluded. It serves pull request URLs of the form https://<host>/<owner>/<name>/pull/<number> with any trailing path, query, or fragment, and builds that form without the suffix as the canonical URL. A readiness probe runs gh auth status --hostname <host>: exit status 0 is ready, another exit status is unauthenticated with the first diagnostic line, and a gh that cannot start is unavailable. A head lookup returns up to 20 open pull requests whose head is the branch, newest first, excluding pull requests from forks; a lookup of the default branch returns none.

Polling returns the first 100 head-commit check contexts without following pages. An incomplete preview sets checksTruncated and keeps GitHub’s aggregate state; its counts do not describe the full list. fetchChecks(ref, signal) reads complete details only for the requested PR, pinning continuation pages to the first response’s rollup. The combined UTF-8 JSON responses must fit maxOutputBytes; excess returns too-large. Failed or non-advancing pages fail only this detail read and leave polling results intact. Runs with the same application, workflow, event, and check name keep only the newest run id; a queued replacement supersedes an older completed run. Runs without a numeric database id are retained by node id because their relative age is unknown. Commit status contexts keep the newest result per context name. Complete lists derive their indicator from these results; unknown context kinds retain GitHub’s aggregate state.

Unfinished check runs and completed runs with stale, missing, or unrecognized conclusions map to pending. Other completed checks map to success, failure (failure, timed out, startup failure, or action required), cancelled, skipped, or neutral. Cancelled checks keep the rollup non-passing. Check runs keep their start and completion times. Commit status contexts map SUCCESS to success, FAILURE and ERROR to failure, and every other state to pending, and carry no times. A GraphQL NOT_FOUND error becomes a not-found failure. A response without GraphQL data or errors, including an HTTP error JSON body, uses the first stderr diagnostic or the body's message. Authentication diagnostics become unauthenticated; oversized check pages become too-large; rate limits and other failures become unavailable. Head lookups preserve the same diagnostic in their rejection.

A pull request is mergeReady when it is open, not a draft, GitHub reports its merge state as CLEAN, HAS_HOOKS, or UNSTABLE, and the signed-in user has write, maintain, or admin permission. mergeMethods lists the squash, merge-commit, and rebase methods the repository allows, the user's default merge method first. Marking ready runs gh pr ready <number> --repo <host>/<owner>/<name>. Merging calls PUT repos/<owner>/<name>/pulls/<number>/merge through gh api with the method and the expected head SHA, so GitHub refuses once new commits arrived, which is reported as stale. Unlike gh pr merge, it never enables auto-merge, never joins a merge queue, and never deletes the head branch. A refused action reports GitHub's message, and a diagnostic that mentions authentication becomes unauthenticated.

diff runs gh pr diff <number> --repo <host>/<owner>/<name> --color never. fileText reads repos/<owner>/<name>/contents/<path>?ref=<commit> through gh api with the raw media type and accepts only a full 40- or 64-digit hexadecimal commit. fileUrl returns https://<host>/<owner>/<name>/blob/<commit>/<path>. Both paths percent-encode each segment. A refused read becomes not-found for HTTP 404, unauthenticated for a diagnostic that mentions authentication, too-large for GitHub's too_large error, which a diff over its own size limit draws, and unavailable otherwise, with GitHub's message. A read whose output exceeds maxOutputBytes becomes too-large, and one that outlives timeoutMs becomes unavailable.

Review submission checks the current pull request head, then posts a single inline comment or one completed review through the REST API with an explicit commit_id. Multiline comments carry their side and inclusive start and end lines. Review decisions are Comment, Approve, and Request changes. JSON request bodies travel on stdin. The provider never retries a mutation: a timeout, unexpected response, or server error after dispatch returns an unknown outcome that the caller must reconcile on GitHub. A commit arriving between the check and the write can make the explicitly addressed review outdated; GitHub does not offer an atomic head precondition on these endpoints.

---

Understand the implementation

Implementation internals — click to expand

A fetch groups references by host and sends one initial gh api graphql query per host. Continuation queries use the original rollup node id, so a changed pull request head cannot mix commits within one check list. The query inlines validated owner, name, and number values and gives each pull request an alias, so partial GraphQL errors fail only their own aliases. gh exits nonzero on partial errors but still prints the complete response, which the provider parses before it inspects the exit code.

Source	Responsibility
src/index.ts	Configuration validation and provider registration
src/provider.ts	URL mapping, host grouping, and failure classification
src/graphql.ts	Query construction and response validation and mapping
src/gh.ts	Host gh execution with environment scrubbing and limits
src/urls.ts	Remote URL and pull request URL parsing

---

Further Exploration

• Forge registry — provider registration and shared polling.
• Forge subsystem — provider contract and change request types.
• Subprocess environment — the shared environment scrub.

---

Model Experience

None, as the provider reads pull request status for host-side watchers without contributing model context.

KV Cache effect

None. Provider output reaches only host-side watchers.

Known Limitations and Deferred Work

• GitHub CLI on the host — gh must be installed and signed in for each configured host; tokens in environment variables are not forwarded. Hosts missing from hosts are never read, including references retained across configuration changes. A status fetch returns unavailable for those references; a head lookup rejects before starting gh.
• First 100 review threads — unresolved threads after the first 100 are not counted.
• No fork discovery — head lookups exclude pull requests whose head is in another repository.
• Rate limits — every poll costs one GraphQL query per host, plus one query per additional page of 100 check records, against the signed-in account’s rate limit.
• No merge queue — a base branch that requires a merge queue refuses a direct merge, and the provider never queues one.

Dev Note

Working context for maintainers — click to expand

None.