Git workflows

Git workflows connect work in Linear to the branches, commits, and pull requests that implement it.

⁠

Keep code connected⁠

When a branch name, pull request title, or commit message includes an issue identifier, Linear links the code change to that issue automatically.

This keeps the issue, code changes, pull request, and discussion together. Anyone viewing the issue can see what is being built and where it is in the development process.

You can use Linear’s suggested branch name, but you do not need to start from the issue for the connection to work.

Let the workflow update itself⁠

Your team can configure Git automations that update issue statuses as a pull request progresses.

For example, an issue can move forward when a pull request is opened, ready for review, or merged. The exact behavior depends on your team’s workflow settings.

Move to review⁠

When a pull request is ready, it enters your team’s review process. The next page explains how to review code changes in Linear.

Read the docs⁠

• Code and reviews. Connecting coding tools and configuring Git automations.
• Reviews. Reviewing pull requests and code changes in Linear.