Merge a pull request from an approval, on a token the pod holds: pinned to the head the person approved, and refused when the head moved, a required check is not green, or the repository is not in the list. One verb, github_merge_pr. Separate from github-read, which never writes.
What your agent can do with it
- github_merge_apiAuthenticated access to the GitHub REST API for github_merge_pr: it reads a pull request and its checks, then merges it. `config.baseUrl` pins api.github.com; `config.auth` inject…
- github_merge_prMerge one pull request, pinned to the head the person approves. Returns { merged, mergeCommitSha, url, detail }. Refuses with the reason (nothing merged) when the repository is no…
What you will need
Asked for at install. Stored in your pod, never on our servers.
- GitHub token (merge)A fine-grained GitHub token. Repository access = ONLY the repositories listed below (never one that lands through a merge queue). Permissions = Pull requests: …
- Repositories it may mergeComma-separated owner/repo, e.g. Synap-core/app-bases,Synap-core/browser. A repository not listed is refused before anything is read.
- Required checksComma-separated check or commit-status names that must be green on the head, e.g. synap/devbox. Empty is refused: a merge with nothing vouching for the head ne…
- {{name}} GitHub token (merge)SecretThe installer's own GitHub token with write access to the listed repositories, used only by github_merge_pr. Not pod-wide.