DocsTools
GitHub
Repos, pull requests, issues and Actions, made as you.
- Category
- Development
- How you connect
- Sign in. You sign in with your account. Homla never sees your password.
- Time to set up
- About 1 minutes
- Actions
- 12 read, 14 write
Connect it#
In Homla, open Connectors, then GitHub. The Setup guide button walks you through the same steps, with fields to paste into.
Who can do it. Each person connects their own GitHub account. Any GitHub user can connect. Homla then does exactly what that account can do on GitHub, nothing more: a repo you can't see on github.com stays invisible, and a branch you can't push to stays protected.
- Open GitHub in Homla and click ConnectIn Homla, open Connectors, then GitHub, then Connect my GitHub account. GitHub opens in a new window. Open it.
- Sign in with the GitHub account that has the reposIf you use several GitHub accounts (personal and work), check the avatar at the top right of GitHub before you continue. Homla sees exactly the repos this account can open.
- Authorize Homla on GitHub's consent screenGitHub lists what Homla may do as you (see the permissions below) and your organizations. Next to each organization, click Grant if it's there, or Request so an owner approves Homla. Then click Authorize; you land back in Homla, connected. What each person can actually do is set in Homla: a read-only role only ever sees the read tools, and every write asks for confirmation first.
Homla acts with your full GitHub rights: through github_rest it can delete a repository you own. Read the confirmation before approving any write.
- Check it worksAsk your assistant "list my GitHub repositories" (github_repos_list), then "show the open pull requests on owner/repo".
- If something goes wrong"Not found, or the connected GitHub account cannot see it": GitHub answers 404 for private repos you can't access; check owner/name, or connect the account that has access. "has not approved Homla": the organization restricts OAuth apps; an owner approves Homla at github.com/organizations/ORG/settings/oauth_application_policy. "SAML single sign-on": open github.com/settings/applications, select Homla and authorize it for that organization. "The GitHub OAuth app is not configured": the Homla server has no GitHub app yet; tell your Homla admin. "Reconnect GitHub": the token was revoked; click Connect again.
What your AI can do#
These are the actions Homla gives your AI. Your role decides which ones you get. Write actions are a dry run until confirmed, see Approvals and dry runs.
Read#
Looks things up, never changes anything.
| Action | What it does |
|---|---|
github_repos_list | List repositories: yours (default), an org's or a user's. |
github_repo_get | Get a repository's metadata, with optional README, branches, tags, languages, topics, collaborators. |
github_file_get | Read a file (text, decoded) or list a directory at a ref. |
github_commits_list | List commits (branch, path, author, since/until), get one commit with its files (sha), or compare base...head. |
github_issues_list | List issues in a repo (or yours across repos without repo). |
github_issue_get | Get an issue (or a PR's conversation) by number, with its comments. |
github_pulls_list | List pull requests. |
github_pull_get | Get a pull request, with optional files (patches), reviews, review comments, commits, check status, raw diff. |
github_runs_list | List GitHub Actions workflow runs (filter by workflow, branch, status, event), or the repo's workflows (workflows=true). |
github_run_get | Get a workflow run with its jobs and steps; logs=true adds the tail of each failed job's log. |
github_releases_list | List releases, or get one by tag, or the latest. |
github_search | Search GitHub: code, issues (and PRs), commits, repositories or users, with GitHub search qualifiers. |
Write#
Creates or changes things, as the account owner.
| Action | What it does |
|---|---|
github_repo_create | Create a repository for you or an org, optionally from a template or as a fork. |
github_branch_create | Create a branch from another branch, tag or sha (default: the repo's default branch). |
github_files_commit | Create, update or delete several files in ONE commit on a branch (created from from if missing). |
github_issue_create | Open an issue with labels (missing labels are created), assignees and a milestone by title. |
github_issue_update | Update an issue or PR: title, body, state (close/reopen, reason), labels (set/add/remove), assignees, milestone. |
github_comment_create | Comment on an issue or a pull request's conversation. |
github_pull_create | Open a pull request from head to base (default branch), optionally draft, with reviewers. |
github_pull_update | Update a PR: title, body, base, state, draft/ready, request or remove reviewers, update branch from base. |
github_pull_review | Review a PR: APPROVE, REQUEST_CHANGES or COMMENT, with a body and optional inline comments. |
github_pull_merge Deletes | Merge a PR (merge, squash or rebase), optionally only at a given head sha, and delete its branch. |
github_run_action | Control GitHub Actions: dispatch a workflow on a ref with inputs, re-run a run, re-run failed jobs, or cancel. |
github_release_create | Publish a release for a tag (created at target if missing): name, notes or generated notes, draft, prerelease. |
github_rest | Any GitHub REST call (1,200+ routes): method, path, query, body. |
github_graphql | Any GitHub GraphQL query or mutation (Projects v2, discussions, ...). |
Disconnect it#
In Homla, open the account menu on the tool's page and choose Disconnect. Anyone it was shared with loses access at once. To cut it off on the tool's side too:
To cut Homla off, open GitHub Settings, Applications, Authorized OAuth Apps, and click Revoke next to Homla. Or click Disconnect on the GitHub page in Homla. An org owner can also withdraw the org's approval under the organization's Third-party access settings.
Generated from the product code. Action names are what the CLI and the API use.