> ## 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. # GitLab > Read GitLab projects, issues, merge requests, comments and wiki pages in Hebno, and create issues and add comments after you confirm. The GitLab integration makes engineering work visible in client delivery. Ask which issues are open on the Contoso pricing model, what a merge request changed before the readout, or what the project wiki says about the data refresh, and Hebno answers from GitLab with each issue, merge request and page cited. When a request implies a change, such as raising an issue or replying on a merge request, Hebno shows a confirmation card and writes to GitLab only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own GitLab account on GitLab.com or your own GitLab instance. | | **Default access** | Read and write | | **Attach** | Projects, issues, merge requests, wiki pages, Markdown files such as `README.md` | | **Search** | Hebno searches GitLab when a request mentions a project, issue or merge request number, label, milestone, assignee or branch | | **Link** | A project links to one or more GitLab projects | | **Write** | Create an issue, add a comment to an issue or merge request. Every write needs a person to confirm. | ## Before you start You need: * A GitLab account with access to the projects you want to use. In a private project, reading merge requests and repository files needs the **Reporter** role or higher. Creating issues and comments needs the **Guest** role or higher. * An allowed integration. An owner or admin sets **GitLab** to **Allow** under **Admin → Connectors → Catalogue**. * For GitLab Self-Managed or GitLab Dedicated, an instance-wide OAuth application. A GitLab administrator creates it under **Admin area → Applications** with the redirect URI shown on the **GitLab** card in Hebno and the scopes below. An owner or admin in Hebno then enters the instance URL, **Application ID** and **Secret** on the card under **Admin → Connectors**. Hebno must be able to reach the instance over HTTPS. Hebno requests these OAuth scopes: | Scope | Why Hebno needs it | | - | - | | `read_user` | Show which GitLab account is connected, and show authors and assignees by name | | `read_api` | Read projects, issues, merge requests, notes, milestones, wiki pages and repository files | | `api` | Create issues and add comments after you confirm. GitLab offers no narrower scope for these writes, and Hebno uses it for nothing else. | GitLab checks your own role on every request, so you see only the groups and projects you can open in GitLab, including confidential issues where your role allows them. ## Connect GitLab **1. Start the connection** Open **Settings → Connections**, find **GitLab** under **Engineering** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Choose your instance** Choose **GitLab.com**, or your organisation's instance if an admin has added one. **3. Authorise Hebno** Sign in to GitLab, review the scopes and select **Authorize**. **4. Return to Hebno** The card shows **Connected** with your GitLab username and instance. Tokens are encrypted at rest. GitLab access tokens expire after two hours, and Hebno renews them automatically. Select **Disconnect** at any time, revoke Hebno in GitLab under **Preferences → Applications**, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. ## What Hebno reads | GitLab object | Fields Hebno uses | Typical questions | | - | - | - | | **Project** | Path, name, description, visibility, default branch, topics, group | "Which GitLab projects do we have for Contoso?" | | **Issue** | IID, title, description, state, labels, assignees, milestone, due date, weight, confidential flag | "What is still open on the Contoso pricing model?" | | **Merge request** | IID, title, description, state, draft flag, source and target branches, reviewers, approvals, pipeline status, merged date | "Which merge requests are waiting for approval?" | | **Comment** | Author, date, body and thread, on issues and merge requests (GitLab notes) | "What did Sarah say on the store cluster merge request?" | | **Milestone** | Title, start and due dates, open and closed issue counts | "How close is the November readout milestone?" | | **Wiki page** | Title, slug, content, last updated | "What does the wiki say about the weekly data refresh?" | | **Markdown file** | `README.md` and other `.md` files on the default branch | "How do we rerun the elasticity model?" | Reads are live. Hebno queries the GitLab REST API when a request needs it, and reads wiki pages and files as they are 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 confidential issues, comments and wiki content from private projects. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | GitLab object | Fields on the card | | - | - | - | | **Create an issue** | Issue | Project, title, description, labels, assignees, milestone, due date, confidential | | **Add a comment** | Note | Issue or merge request, comment text | ![Confirmation card for GitLab with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-gitlab.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=2cd42fed32da82b8e58670d01d978de6) A GitLab change pending confirmation. Nothing is written until you confirm. Hebno never pushes code, creates branches, merges, approves or closes merge requests, closes issues, edits wiki pages, or changes project settings. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant GitLab You->>Hebno: Raise an issue to check the store cluster outliers Hebno->>GitLab: Find the Contoso pricing project, labels and milestones GitLab-->>Hebno: northwind/contoso-pricing-model, milestone November readout Hebno-->>You: Confirmation card with project, title, description, assignee You->>Hebno: Confirm Hebno->>GitLab: Create the issue as you GitLab-->>Hebno: Issue #31 created Hebno-->>You: Done, with a link to the issue ``` Writes are made with your own token, so GitLab shows you as the author. ## Link a project to a GitLab project Linking marks which GitLab projects belong to an engagement, so you can ask "what is still open?" without naming the GitLab project. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **GitLab**. 3. Search by group or project path and select it. Repeat for each GitLab project in the engagement. In chats tagged to the project, Hebno starts with the linked GitLab projects for any issue, merge request or wiki question, and cards for new issues default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use GitLab in chat * **Attach**: open the **+** menu, choose **Sources → GitLab**, and pick a project, an issue, a merge request, a wiki page or a Markdown file. Or type `/` and choose **GitLab**. * **Ask**: name the project, issue number or person in your request. For example: > List the open issues on the Contoso pricing model due before 20 November, with owners. > Summarise what the merge requests merged this week changed, using the wiki for context. > Comment on merge request 27 that Priya Nair checked the outputs against the client extract. * **Research runs** show a **Checking GitLab** step, with a chip for each project, issue, merge request and page it read. * **Agents** can read GitLab on a schedule, for example a Friday summary of merge requests waiting for approval. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **404 Project Not Found** for a project you expect | Your GitLab role does not include the project, or it belongs to a group you are not a member of. Ask a maintainer for access. | | A write fails with **403 Forbidden** | Your role in the project cannot create issues or comment, or the project has issues turned off under **Settings → General → Visibility, project features, permissions**. | | A write fails with **insufficient\_scope** | The authorisation predates the `api` scope. Select **Disconnect**, then **Connect** and approve again. | | **Connect** fails for your own instance | Check the instance URL, **Application ID** and **Secret** on the card, and that the redirect URI in **Admin area → Applications** matches the one Hebno shows. | | **Reconnect GitLab** appears | The authorisation was revoked in **Preferences → Applications** or the refresh token is no longer valid. Select **Connect** to authorise again. | | Requests fail with **429 Too Many Requests** | GitLab limits authenticated API requests per minute. Wait 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) * [GitHub](https://hebno.com/docs/integrations/github.md) * [Jira](https://hebno.com/docs/integrations/jira.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.