Git Branch Names from Linear Issue Identifiers

Linear Issue Branch Names

Linear uses team-prefixed identifiers (e.g., ENG-123, DES-456, PLAT-789) similar to JIRA but with a more streamlined workflow. Linear has built-in git integration that automatically detects branch names containing issue IDs and updates issue status accordingly.

Standard Format

{type}/{linear-id}-{description}

Examples

Linear Issue	Title	Branch Name
ENG-123	Build notification system	feature/eng-123-build-notification-system
DES-456	Update button components	feature/des-456-update-button-components
PLAT-789	Fix Redis connection pool	bugfix/plat-789-fix-redis-connection-pool
MOB-101	Add biometric login	feature/mob-101-add-biometric-login

Linear Git Integration

Linear's git integration provides powerful automatic behaviors when branch names contain issue IDs:

1. Auto-transition — When a branch is created with the issue ID, Linear can automatically move the issue to "In Progress"
2. PR linking — When a PR is opened from a branch with the issue ID, Linear links the PR to the issue
3. Auto-close — When the PR is merged, Linear can automatically move the issue to "Done"

Linear's Built-in Branch Copy

Linear provides a "Copy git branch name" button on each issue that generates a branch name in the format username/eng-123-description. You can use this tool to customize that format or standardize it across your team.

Team-Specific Patterns

Linear's team prefixes naturally organize branches by domain:

Team	Prefix	Example Branch
Engineering	ENG-	feature/eng-123-api-redesign
Design	DES-	feature/des-456-component-library
Platform	PLAT-	chore/plat-789-terraform-upgrade
Mobile	MOB-	feature/mob-101-offline-mode

This makes it easy to filter branches by team in CI/CD dashboards or git hosting platforms. The team prefix provides context that a generic number alone cannot.