Swarmz
IntegrationsDeveloper and infrastructure

GitHub API

Read repositories, branches, issues, pull requests, and files, then run bounded repository workflows

GitHub API gives a project server-side access to repository data. It is separate from the GitHub connection used to sync a Swarmz project with a repository.

Before you connect

A Swarmz administrator must create a dedicated GitHub OAuth App for this connector. Do not reuse the project-sync OAuth App: GitHub OAuth Apps accept one callback URL, and the two flows use different callbacks. Enter the client ID and secret on the GitHub API OAuth application admin card, use the callback URL shown there, test the connection, then enable the connector.

With read access, GitHub exposes public repositories available to the user. GitHub's classic repo scope grants both read and write access to public and private repositories; it cannot grant private source-code read access without write access. Request write access only when the workflow needs private repositories or repository changes.

Available operations

OperationWhat it doesLimit per minute
list_repositoriesLists repositories visible to the authorized user30
list_branchesLists branches in one repository30
list_issuesLists repository issues30
list_pull_requestsLists pull requests30
get_fileReads one file or directory listing30
create_issueCreates one issue15
add_issue_commentComments on an issue or pull request15
update_fileCreates or updates one file with a commit message10

update_file accepts at most 5 MB of base64 content and rejects path traversal. Updating an existing file requires its current SHA from GitHub.

Connect and verify GitHub API

Ask the AI for a repository workflow, select Connect new, and approve the requested GitHub access.

  1. List repositories and confirm a disposable test repository.
  2. List its branches, issues, and pull requests.
  3. Read README.md.
  4. Create an issue named Swarmz connector test and add a comment.
  5. If file writes are required, create a test file on a test branch and confirm the commit in GitHub.
  6. Close the issue and remove the branch or test file in GitHub.

Organization SAML or OAuth restrictions can block an otherwise valid token. Authorize the OAuth App for the organization, then reconnect. Generated browser code must not call GitHub directly; the project server route calls the Swarmz connector gateway.

On this page