Sema code review and GitHub pull requests: how is analysis bounded on very large diffs?
Integration boundary We are evaluating the Sema code-review tool connected to GitHub, where automated review comments are posted directly onto pull requests. The boundary in question is between Sema's analysis engine and the GitHub pull-request API. Goal Understand what happens when a pull request exceeds a practical size — many changed files, a very large d
sema