Baz Docs
Sign Up ↗Contact sales
  • Introduction
  • Basics
    • Organization Setup
    • Configure with GitHub
    • Model Context Protocol (Beta)
  • Integrations
    • Datadog
    • GitHub Actions
    • Slack
    • Jira
    • Linear
  • Agents
    • Baz Reviewers
    • Custom Reviewers (Beta)
    • Working with Agents
  • changes
    • Code Review
      • Description
      • Topics
        • Commands
      • Diff
        • Git Diff (optional)
      • Merge eligibility
    • Chat
    • Discuss
  • Code
    • Overview
  • Notifications
  • Account
    • Plans & Usage
    • Billing
    • Security, privacy and compliance
Powered by GitBook
On this page
  • Configuring Baz & Linear
  • How Baz Uses Linear Issue Data
  1. Integrations

Linear

Baz's Linear Integration

PreviousJiraNextBaz Reviewers

Last updated 4 days ago

By pulling in issue information like titles, descriptions, issue states and labels, and stakeholder comments, Baz ensures that every change request is grounded in intent. Reviewers no longer need to flip between Linear and GitHub to understand why a change exists—they get the full story, right where the code is.

Baz uses this context to:

  • Enrich AI-generated summaries and topics with your business objectives.

  • Tailor prompts to reflect the goals and constraints from the Linear issue.

  • Help reviewers focus on what’s important by aligning code changes to the original intent.

Configuring Baz & Linear

  1. In Baz, open Settings → Integrations → Linear.

  2. Click Connect and follow the OAuth flow.

  3. Once authorized, Baz will automatically attach issue context to any linked change request.

Tip: Baz detects linked issues by conventional branch names (e.g. team-slug-123) or by issue IDs mentioned in the PR description (e.g. #123).

How Baz Uses Linear Issue Data

Once enabled, Baz pulls these fields from linked Linear issues:

  • Title & Description – to inform review summaries and reasoning.

  • Issue State & Labels – to set expectations (e.g. bug vs. feature vs. chore).

  • Stakeholder Comments – injected into review prompts as context.

This context powers workflows that:

  1. Generate summaries that reflect your Linear objectives.

  2. Break down topics based on feature or flow relevance.

  3. Guide reviewers to evaluate changes through the lens of what the issue was designed to accomplish.

Configure Linear