Sourcery
@sourceryai.bsky.social
Code reviews on every pull request in seconds
How much time per week are you spending on fixing CI failures?
We're working on some extensions to our code reviews/GitHub integrations in this area and we're trying to better understand what other teams are running into
We're working on some extensions to our code reviews/GitHub integrations in this area and we're trying to better understand what other teams are running into
September 5, 2024 at 12:57 PM
How much time per week are you spending on fixing CI failures?
We're working on some extensions to our code reviews/GitHub integrations in this area and we're trying to better understand what other teams are running into
We're working on some extensions to our code reviews/GitHub integrations in this area and we're trying to better understand what other teams are running into
Keeping your PRs small can seriously speed up your team.
We dug into the data of ~10k PRs from different orgs to see what drove the most impact on development metrics
The biggest factor on lead time to merge was PR size
PRs < 150 changed lines were merged way faster than PRs > 150 lines
We dug into the data of ~10k PRs from different orgs to see what drove the most impact on development metrics
The biggest factor on lead time to merge was PR size
PRs < 150 changed lines were merged way faster than PRs > 150 lines
September 4, 2024 at 2:38 PM
Keeping your PRs small can seriously speed up your team.
We dug into the data of ~10k PRs from different orgs to see what drove the most impact on development metrics
The biggest factor on lead time to merge was PR size
PRs < 150 changed lines were merged way faster than PRs > 150 lines
We dug into the data of ~10k PRs from different orgs to see what drove the most impact on development metrics
The biggest factor on lead time to merge was PR size
PRs < 150 changed lines were merged way faster than PRs > 150 lines