Tools
Ten tools become available once a repo is attached. Each one has its own page with the full detail.
Reference
| Tool | What it does |
|---|---|
| github_read_file | Fetches a file directly from GitHub, for one not included in the local clone. |
| github_search_code | Searches code across the entire repo on GitHub, not just the local clone. |
| github_list_commits | Lists recent commits on the active branch. |
| github_commit_files | Commits the current state of the sandbox clone to the working branch. |
| github_upload_file | Commits a single file, including binary files, to the active branch. |
| github_create_pull_request | Opens a pull request from the working branch into the default branch. |
| github_list_issues | Lists open issues in the active repo. |
| github_create_issue | Creates a new issue in the active repo. |
| github_comment_on_issue | Posts a comment on an existing issue or pull request. |
| github_list_pull_requests | Lists open pull requests in the active repo. |
Working in the sandbox clone
Most of tAI's work happens directly on the local clone of your repo, using its normal file-reading and file-editing tools rather than a dedicated GitHub tool for every read. github_read_file and github_search_code exist as a fallback for anything too large to have been cloned.
Committing changes
github_commit_files, github_upload_file, and github_create_pull_request cover pushing changes back to GitHub. Nothing is ever pushed straight to the default branch: the first commit in a conversation creates a dedicated working branch, and a pull request opens from that branch when the work is ready for review.
Issues & pull requests
github_list_issues, github_create_issue, github_comment_on_issue, and github_list_pull_requests cover the active repo's issue tracker, separately from any code changes.