Git API Reference

Every operation of the Git API, under /git/api. Sign requests with an access key (Authorization: EWS-ACCESS-KEY <id>:<secret>). A successful JSON response is { "success": true, "data": … }.

repositories

Repositories served by the platform itself

branches

Refs, and the console-side equivalent of pushing to them

tags

Tag refs

commits

History, individual commits, and console-made commits

files

Reading the working tree at a ref

pulls

Pull requests, backed by real merges

merge-queue

A protected branch's merge queue (GitHub's merge queue)

releases

Named, published tags; publishing one starts `on: release` workflows

release-assets

Files attached to a release — binaries, archives, checksums

security

Security & quality: the security policy, secret scanning, dependency and code scanning alerts

issues

Issues: bugs, tasks and CI alerts, with labels, assignees and comments

labels

A repository’s labels, shared by its issues and pull requests

tag-protection

Tag patterns only holders of git:PushProtectedTag may create, move or delete

commit-statuses

Pass/fail an external tool reports on a commit; a required check can name one

branch-protection

Rules that constrain what may land on a branch

deploy-keys

Per-repository SSH keys for machines

webhooks

Outbound notifications on repository events

webhook-deliveries

A webhook's recent deliveries (30 days), and sending one again

access-tokens

HTTP credentials for cloning and pushing

ssh-keys

Your SSH public keys for git over SSH

attachments

Images and video attached to pull request comments

github

Connect GitHub: installations of the platform's GitHub App, repositories mirrored and pushed back through them

Generated from the API description, the same one the API checks requests against and the CLI is built from.