Engineering · Easy
Move issues along when code is merged
Updating issue status by hand after every pull request is easy to forget, so boards drift from reality. Linking them keeps status accurate.
Software used
Has a free plan
GitHub
What happens
When
A pull request that mentions a Linear issue is opened or merged on GitHub.
Then
- The issue moves to in progress when the pull request opens.
- It moves to done when the pull request merges.
How the tools connect
With a built-in integration. Linear lists GitHub as an integration on its website.
Set it up
Connect GitHub in Linear's settings and choose the repositories.
Use the issue ID in branch names or pull request titles.
Check the status rules match how your team works.
Menus change, so these steps say what to do rather than where to click. Each company's help pages have the current screens.
Watch out for
- Pull requests that touch several issues need each issue ID mentioned.
Track these tools in My stack
Add the software you pay for and see which automations you can set up with it.
Ideas for my stackRelated automations
Engineering · Some setup · Built-in integration
Turn app errors into issues the team will fix
Errors seen only in a monitoring tool are easy to ignore. Creating an issue from the error puts it into the normal planning flow, with the stack trace attached.
Engineering · Easy · Built-in integration
Tell the team the moment your site goes down
Finding out about downtime from customers is the worst way. An alert in the channel the team already watches gets someone looking within minutes.
Engineering · Easy · Built-in integration
Follow code changes in a team channel
Pull requests waiting for review slow everyone down. Posting them where the team talks gets reviews done sooner and keeps others aware of what's shipping.
