Connecting GitHub
Connecting GitHub lets agents help with your code and project activity — like reviewing changes, working with issues, or opening pull requests. This article explains how to connect it and what to expect.
Why connect GitHub
With GitHub connected, you can ask for things like:
- Summarizing recent activity in a repository
- Reviewing a change and noting issues
- Drafting or commenting on an issue
- Opening a pull request from work an agent has done
If you don't work with code, you may not need this connection — it's mainly for software projects.
How to connect
- Go to the integrations area of your workspace.
- Find GitHub in the list of available connections.
- Choose to connect it. You'll be taken to GitHub to sign in.
- Choose which repositories to grant access to, and review the permissions.
- Approve, and you'll return to Hirebase with GitHub connected.
The sign-in happens securely on GitHub's side. Hirebase never sees your GitHub password.
Grant access only where you need it
When connecting, you can usually limit access to specific repositories rather than your whole account. Granting the narrowest access that still covers your tasks is a good habit.
What permissions are used for
The access you grant lets agents work with the repositories you've shared, only as part of the tasks you give them.
Changes are reviewed
Actions that affect a repository — like opening a pull request or commenting — will pause for your approval before they happen, even when a task is set to act automatically. You'll see what the agent intends to do first.
If the connection stops working
If GitHub access is revoked or expires, agents won't be able to use it until you reconnect. If a task reports it can't access GitHub, reconnect it from the integrations area.
Disconnecting
You can disconnect GitHub at any time from the integrations area. See Managing connected integrations.