Linear | HookCI docs

The Linear integration is meant to file an issue when a run fails on a branch you care about, so broken builds do not depend on someone remembering to report them.

What it will do

Create an issue for a failed run on a configured branch, such as main.
Put the repo, branch, commit, failed job names, and a signed link to the logs in the issue body.
Avoid duplicates: a repeat failure of the same job on the same branch is meant to add a comment to the open issue instead of creating a new one.
Move the issue to a done state, or comment on it, when a later run passes. Whether it closes the issue automatically is a design question and will be configurable.

Illustration. Design of an issue auto-created from a failed run, with a link back to the run.

Connect flow (design)

Pair an agent and watch a repo first. See Pair an agent.
In the hub settings, choose Connect Linear and approve the OAuth request for your Linear workspace.
Pick the team that receives issues and, optionally, default labels.
Enable it per repo in .hookci.yml.

Configuration (design)

The linear key is a design placeholder. It is not accepted by the current schema.

notify:
  linear:
    team: ENG
    on: [failure]
    branches: [main]
    labels: [ci]

Until release, use Slack or GitHub Checks for failure reporting. The other notification keys are documented in the .hookci.yml reference.

Data

The integration is expected to send only run metadata and a log link to Linear, never source code. Linear credentials would be stored encrypted by the hub and removed when you disconnect or uninstall. See Security and data.