Supported operations
- List and inspect repositories, including private repositories
- Read repository files, issues and pull requests
- Create repositories, commits, issues and pull requests
GitHub integration
Work with repositories through controlled operations
Inspect repositories, files, issues and pull requests, then create supported GitHub items only after an explicit request and your chosen approval policy.
The GitHub connector supports private repositories when the connected account grants the repo scope. Read operations can list and inspect repositories, open files at a branch or reference, list issues and pull requests, and search repositories or issues with GitHub query syntax. These structured reads are useful for reviewing code and project state without scraping repository pages.
Explicit writes can create a repository, save a complete file as a commit, open an issue or create a pull request. Each write needs exact repository coordinates in owner/name form. Pull requests additionally require an existing source branch and target branch; a profile URL, organisation name or natural-language branch label is not enough and must never be guessed.
Current boundaries
- The GitHub repo scope grants broad provider-level read and write access.
- Writes require an explicit request and may require confirmation.
- Branch and repository identifiers must be verified before a write.
How to connect
- 1Connect GitHub and review the repo, profile and email permissions.
- 2Choose operation-level Allow, Ask or Deny policies.
- 3Keep consequential writes set to Ask unless automatic execution is intended.
“Open a pull request from my existing feature branch.”
Use synthetic or your authorised account data, then review the returned result in the conversation.
How to use GitHub reliably
- The repo scope is broad at the provider level, so operation-level Allow, Ask and Deny rules are the narrower control inside resolvenengine. Consequential writes should normally remain on Ask.
- Saving a file sends the complete new content and a commit message. Updating an existing path may require its current blob identifier, which protects against replacing a changed file blindly.
- The connector does not advertise merging or closing pull requests, deleting repositories, managing secrets or running arbitrary Git commands. Provider validation errors are returned as decided failures, not uncertain writes.
Prompt examples
“List my private repositories and show the five most recently updated.”
“Read README.md from the default branch of owner/repository.”
“Create an issue from this reviewed bug report in owner/repository.”
“Open a pull request from the existing feature branch to the verified default branch after approval.”
Rate limits and freshness
GitHub has primary limits based on authentication type, plus secondary limits for request patterns and separate limits for search. Responses expose rate-limit and retry headers. Because one task can combine repository, search and write endpoints, the connector should follow the returned headers rather than present one number as a universal allowance.
GitHub REST API rate limitsIncluded with Pro at $19 USD/month. Bring your own AI API key; provider charges are separate.
Ready to work in your own Chrome?
Install resolvenengine from the Chrome Web Store. Sign-in, subscription and billing happen inside the extension.