Regression detection should provide possible culprits based on git history #275
Labels
dx
Developer experience
enhancement
New feature or request
infrastructure
Work related to infrastucture
regression
If we detect a regression, it would be great if the CI job can already check the git histories of our most important upstream packages and print possible changes that could cause a regression in a given timewindow
See also #271 (comment)
The text was updated successfully, but these errors were encountered: