All Categories ​>​ ​Using LinearB Insights

Using LinearB Insights

How to - Handle Large Pull Request

How to - Handle Large Pull Request. Why Is It a Problem? Small and digestible pull requests, helps developers to "cap" the risk of introducing new bugs or "break" production. When the pull requests d…

Updated 1 year ago by Eran Shitrit

How to Address Hanging Review Requests and Long Reviews

Reviews are important "team" task. Reviews affect both quality of code and delivery. Hanging reviews slows down the cycl…

Updated 2 years ago by Boaz Dremer

How to Address High Risk Work

How to Address High-Risk Work. What is high-risk work?. LinearB classifies high-risk work as branches with more than 100 code changes, and also over 50% of these changes are rework or refractor work.…

Updated 1 year ago by Betsy Rogers

How to Address Pull Request Merged w/o Review or with Basic Review

How to Address Pull Request Merged w/o Review or with Basic Review. Why Is It a Problem? Even the best developers can make mistakes or miss things. After coding for a period of time and self-testing,…

Updated 1 year ago by Betsy Rogers

What do I do if my coding time is high?

Continuous improvement works best when your team is breaking work into manageable chunks. Here are 3 ways to reduce your coding time using LinearB.

Updated 1 month ago by Betsy Rogers

What do I do if my pickup time is high?

It's integral to a continuously developing team to be reviewing code as close to real-time as possible. Here are ways to reduce your pickup time using LinearB

Updated 2 years ago by Betsy Rogers

What do I do if my review time is high?

It's integral to a continuously developing team to be reviewing code as close to real-time as possible. Here are some ways to reduce review time.

Updated 1 year ago by Betsy Rogers

Powered by HelpDocs (opens in a new tab)