> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # GitHub > Read GitHub repositories, issues, pull requests, comments and README files in Hebno, and create issues and add comments after you confirm. 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 | | | | - | - | | **Connection** | Personal connection. Each member connects their own GitHub account. | | **Default access** | Read and write | | **Attach** | Repositories, issues, pull requests, Markdown files such as `README.md` | | **Search** | Hebno searches GitHub when a request mentions a repository, issue or pull request number, label, milestone, assignee or branch. It builds the GitHub search query for you. | | **Link** | A project links to one or more GitHub repositories | | **Write** | Create an issue, add a comment to an issue or pull request. Every write needs a person to confirm. | ## 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: | Permission | Access | Why Hebno needs it | | - | - | - | | **Metadata** | Read | List repositories, branches, collaborators and topics | | **Contents** | Read | Read `README.md`, files under `docs/` and other Markdown files on the default branch | | **Issues** | Read and write | Read issues, labels, milestones and comments, and create issues and comments after you confirm | | **Pull requests** | Read and write | Read pull requests, reviews and review comments, and comment on pull requests after you confirm | 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 | GitHub object | Fields Hebno uses | Typical questions | | - | - | - | | **Repository** | Owner, name, description, visibility, default branch, topics, languages | "Which repositories do we have for Contoso?" | | **Issue** | Number, title, body, state, labels, assignees, milestone, author, opened and closed dates | "What is still open on the Contoso pricing model?" | | **Pull request** | Number, title, body, state, draft flag, base and head branches, requested reviewers, review state, changed file names, merged date | "What did the last merged pull request change in the elasticity model?" | | **Comment** | Author, date, body, on issues, pull requests and review threads | "What did Sarah say on the pull request about store clusters?" | | **Review** | Reviewer, state (approved, changes requested, commented), summary | "Which pull requests are waiting for a review?" | | **Milestone** | Title, due date, open and closed issue counts | "How close is the November readout milestone?" | | **Markdown file** | `README.md`, files under `docs/` and other `.md` files on the default branch | "How do we rerun the price elasticity model?" | 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. > [!WARNING] > > 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**. | Action | GitHub object | Fields on the card | | - | - | - | | **Create an issue** | Issue | Repository, title, body, labels, assignees, milestone | | **Add a comment** | Issue comment | Issue or pull request, comment text | ![Confirmation card for GitHub with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-github.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=c2b7f2b0c324bdcedd15bbb4bfdec1a6) 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. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant GitHub You->>Hebno: Raise an issue to rerun the model with the November extract Hebno->>GitHub: Find the Contoso pricing repository, labels and milestones GitHub-->>Hebno: northwind/contoso-pricing-model, milestone November readout Hebno-->>You: Confirmation card with repository, title, body, labels, assignee You->>Hebno: Confirm Hebno->>GitHub: Create the issue as you GitHub-->>Hebno: Issue #48 created Hebno-->>You: Done, with a link to the issue ``` Writes are made with your user access token, so GitHub shows you as the author, with the Hebno app badge next to your name. ## Link a project to a repository 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](https://hebno.com/docs/projects/linked-records.md). ## 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](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | A repository you can open in GitHub does not appear | The Hebno app is not installed on that organisation, or the installation covers **Only select repositories**. Ask an organisation owner to add the repository under **Settings → GitHub Apps → Configure**. | | A write fails with **Resource not accessible by integration** | The app installation lacks **Issues** or **Pull requests** write access, or you have read access only. Ask an organisation owner to accept the updated permissions, or ask for write access to the repository. | | Creating an issue fails with **Issues are disabled for this repo** | Issues are turned off in the repository's **Settings → General → Features**. Turn them on or choose another repository. | | A write fails on an archived repository | Archived repositories are read-only in GitHub. Unarchive it or raise the issue elsewhere. | | **Reconnect GitHub** appears | The authorisation was revoked or the refresh token expired. Select **Connect** to authorise again. | | Requests fail with an API rate limit message | GitHub limits requests per user per hour. Wait for the limit to reset and retry. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [GitLab](https://hebno.com/docs/integrations/gitlab.md) * [Jira](https://hebno.com/docs/integrations/jira.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.