Use Ada in GitHub
Use Ada in GitHub when your team wants help inside issues and pull requests. Ada answers where the code review, planning, or bug discussion is already happening.
Who This Guide Is For
Use this guide if you are:
- a GitHub organization owner or repository admin adding Ada
- a Lovelace workspace owner reviewing what GitHub access means
- a contributor who wants to mention Ada in an issue or pull request
- a support or success teammate helping someone fix Ada in GitHub
What Ada Can Do In GitHub
Use Ada when the request belongs in a GitHub conversation:
| GitHub situation | What Ada does |
|---|---|
| An issue has a long discussion | Ada summarizes the thread. |
| A pull request needs review context | Ada explains what changed or what still needs attention. |
| A teammate asks for next steps | Ada suggests a path forward based on the visible discussion. |
| A repository has many active threads | Ada answers where it is mentioned instead of moving work elsewhere. |
Install Ada only on organizations and repositories where the team wants Ada to participate.
Before You Add Ada
GitHub uses the permissions of the person installing the app. Organization owners install apps for an organization. Repository admins install apps for the repositories they administer when organization-wide access is not required. When an organization requires owner approval, GitHub sends the request to an owner instead of installing immediately.
You also need access to the Lovelace workspace where your team uses Ada and permission to connect apps for that Lovelace workspace.
What GitHub Will Ask You To Approve
GitHub asks where Ada is installed and which repositories Ada uses. GitHub also shows what Ada is allowed to do.
The review screen lists these jobs:
| What Ada needs to do | Why it matters |
|---|---|
| See selected repositories | Lets Ada understand the issues or pull requests where Ada is mentioned. |
| Read issue and pull request conversations | Gives Ada the discussion needed to answer. |
| Add comments | Lets Ada answer in GitHub. |
| Notice when Ada is mentioned | Lets Ada start from the conversation where help is requested. |
| Read basic organization or member details | Lets Ada connect GitHub activity to the right Lovelace workspace and person. |
Choose selected repositories unless your team intentionally wants Ada available across every repository in the organization.
Add Ada To GitHub
- Open the GitHub connection flow from Lovelace.
- Choose the GitHub account or organization where Ada is installed.
- Choose all repositories or selected repositories.
- Read GitHub's review screen.
- Approve, install, or request owner approval from the GitHub screen.
- Open a test issue or pull request in a selected repository.
If GitHub shows a request button instead of an install button, an organization owner must approve the request before Ada answers.
Use Ada In GitHub
Mention Ada in a supported issue or pull request conversation:
Ada, can you summarize this thread?
Ask Ada to focus on the visible conversation:
Ada, what are the unresolved questions in this pull request?
Keep requests specific. Ada works best when the issue or pull request already contains the context the team wants Ada to use.
Account Connection
Ada asks a person to connect their GitHub profile to Lovelace when Ada needs to connect GitHub work to the same Lovelace account the person uses elsewhere.
Connecting a GitHub profile does not make the person a GitHub organization owner and does not share their Lovelace account with other GitHub users.
Admin Controls And Disconnect
GitHub organization owners and repository admins review installed apps in GitHub settings. GitHub settings show app permissions, repository access, temporary blocks, and removal controls.
Disconnecting GitHub:
- stops Ada from answering in repositories that are no longer connected
- removes Lovelace's access to the removed organization or repositories
- keeps Lovelace conversations and Library resources that belong to users
To reconnect, start the GitHub connection flow again and choose the organization or repositories where Ada belongs.
Data And History
Ada uses GitHub issues, pull requests, and comments where Ada is asked to help. Disconnecting GitHub removes GitHub access, but it does not delete Lovelace-owned conversations or Library resources.
Troubleshooting
| What you see | What to check |
|---|---|
| You cannot install Ada | Make sure you are an organization owner or repository admin with permission to add apps. |
| GitHub shows a request instead of install | An organization owner must approve the app request. |
| You cannot choose the repository | Confirm the repository belongs to the selected organization and that you have permission there. |
| Ada does not answer | Confirm Ada is installed for that repository, then mention Ada again in a new comment. |
| Ada asks you to connect your account | Follow the account connection prompt so Ada knows which Lovelace account is yours. |
| Ada answered before but stopped | Check whether Ada was removed from the repository or organization. |
| Disconnect did not delete Lovelace history | This is expected. Disconnecting GitHub removes GitHub access, not user-owned Lovelace work. |