How should we think about automating code review? #252
Unanswered
baristaGeek
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're already contextualizing PRs with passive documentation from various sources. Could this information be useful to automate PR review, and provide a "first health-check" for a PR? Something like "according to what I found on Jira and Slack, this PR looks like it could meet the business requirements".
How should we be thinking about this spike?
Beta Was this translation helpful? Give feedback.
All reactions