Skip to main content
The GitHub integration makes engineering work visible in client delivery. Ask which issues are still open on the Contoso pricing model repository, what changed in a pull request before the readout, or what the README says about running the model, and Hebno answers from GitHub with each issue, pull request and file cited. When a request implies a change, such as raising an issue or replying on a pull request, Hebno shows a confirmation card and writes to GitHub only after you confirm.

​
At a glance

​
Before you start

You need:
  • A GitHub account with access to the repositories you want to use.
  • An allowed integration. An owner or admin sets GitHub to Allow under Admin → Connectors → Catalogue.
  • The Hebno GitHub App installed on each GitHub organisation whose repositories you want to read. A GitHub organisation owner installs it under Settings → GitHub Apps, or approves your installation request. On a personal account, you install it yourself during Connect.
Hebno connects as a GitHub App and requests these repository permissions: Hebno also reads your GitHub user profile to show which account is connected. Hebno acts with a user access token, so GitHub checks both the app’s permissions and your own access on every request. A repository you cannot open in GitHub is not visible in Hebno.

​
Connect GitHub

1

Start the connection

Open Settings → Connections, find GitHub under Engineering and select Connect. You can also select Connect from the prompt in a chat.
2

Authorise the app

Sign in to GitHub and select Authorize. If the app is not installed where your repositories are, choose the organisation or account, then All repositories or Only select repositories, and select Install. In an organisation you do not own, GitHub sends an installation request to the organisation owners instead.
3

Return to Hebno

The card shows Connected with your GitHub username and the organisations Hebno can reach.
Tokens are encrypted at rest. Hebno renews them automatically. Select Disconnect at any time, revoke the app in GitHub under Settings → Applications → Authorized GitHub Apps, or ask an admin to revoke the connection under Admin → Connectors → Connections.

​
What Hebno reads

Reads are live. Hebno queries GitHub when a request needs it, and reads files as they are on the default branch at that moment. Hebno does not read source code files, commits or diffs line by line. Only what a reply used is stored with the conversation as its sources.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including issue bodies and comments from private repositories.

​
What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for GitHub with editable fields

A GitHub change pending confirmation. Nothing is written until you confirm.

Hebno never pushes code, creates branches, merges or closes pull requests, submits reviews, closes issues, or changes repository settings. Writes are made with your user access token, so GitHub shows you as the author, with the Hebno app badge next to your name. Linking marks which repositories belong to an engagement, so you can ask “what is still open?” without naming the repository.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then GitHub.
  3. Search by owner or repository name and select it. Repeat for each repository in the engagement.
In chats tagged to the project, Hebno starts with the linked repositories for any issue or pull request question, and cards for new issues default to them. See Linked records.

​
Use GitHub in chat

  • Attach: open the + menu, choose Sources → GitHub, and pick a repository, an issue, a pull request or a Markdown file. Or type / and choose GitHub.
  • Ask: name the repository, issue number or person in your request. For example:
    List the open issues on the Contoso pricing model labelled data-quality, grouped by assignee.
    Summarise the pull requests merged since 26 October and what they changed, for the steering committee update.
    Comment on pull request #45 that Priya Nair reviewed the store cluster outputs and they match the client extract.
  • Research runs show a Checking GitHub step, with a chip for each repository, issue, pull request and file it read.
  • Agents can read GitHub on a schedule, for example a Friday list of issues opened and closed on the engagement repositories. Writes an agent proposes appear in agent approvals for review.

​
Troubleshooting