Skip to main content
Use Linear issue titles and descriptions to help understanding checks explain why a change exists. One shared connection can serve several repositories, each with its own allowed teams and projects.

​
Connect your workspace

You must be a Second Flow workspace owner to connect Linear or change a repository scope.
  1. Open Context Gateway in the Second Flow console.
  2. Open the Linear configuration and select Connect Linear.
  3. Authorize read-only access to the intended Linear workspace.
  4. Return to Second Flow and confirm the connection is active.
If authorization is unavailable, contact us for help with your workspace’s connection.

​
Choose a repository scope

  1. Open Repositories, choose a repository, and open Context Gateway.
  2. Select Configure on the Linear card.
  3. Select at least one allowed Linear team. Optionally select projects to narrow the scope.
  4. Approve the audience using I authorize selected issue content for people who can access this repository’s understanding checks.
  5. Select Save repository scope and verify that the source’s switch is enabled.
When you select projects, an issue must belong to both an allowed team and an allowed project. Selecting a project does not authorize every issue in it for retrieval.

​
Reference an issue in a pull request

Include the issue’s full Linear URL or identifier, such as ENG-123, in the pull-request title, description, or branch name. Second Flow retrieves only explicitly referenced issues within the saved repository scope. An unreferenced issue is not discovered through broad search or linked-issue traversal. Only issue titles and descriptions, including acceptance criteria written in the description, become evidence. Comments, attachments, project briefs, and milestones are outside this integration’s scope.

​
Read and manage context

Issue content is read on demand when generating a new understanding check. Editing the issue does not rewrite existing questions or completed results. Source-dependent operations verify current access and the original content fingerprint. Audience approval allows selected issue content to support checks for the repository’s audience. Review that audience even when Linear itself is private. Disable the repository source to pause retrieval while keeping its selection. Disconnecting the shared connection stops new retrieval and keeps repository scopes for reconnect. Reconnect to the same Linear workspace; to choose another workspace, delete the existing connection and its live scopes first. Deleting a connection removes its live repository scopes. Second Flow does not edit or delete your Linear issues.

​
Troubleshooting

  • An issue was not used: Confirm its explicit reference, allowed team, optional project restriction, and the repository source switch.
  • No teams or projects are available: Check the connected account’s access in Linear, then reload the configuration.
  • Reconnect required: Ask the workspace owner to reconnect the same Linear workspace.
  • Content is unavailable or too large: Keep references focused and reduce the source material where appropriate. Retrieval limits produce an explicit outcome rather than silently truncating an issue.