The other end of the spectrum is linting and tests, which catch errors before review.
Does Ellipsis have a role between these two? If so, what is the role?
Ellipsis will use your existing lint/test commands when making code changes. For example, you can leave a comment on a PR that says "@ellipsis-dev fix the assertion in the failing unit test" and Ellipsis will run the tests, observe the failure, make the code change, confirm the tests pass, lint-fix the code, and push a commit or new PR
Why run it as part of a PR then? I'd prefer to run a tool like this before a PR is even open, and ideally on my local machine.
Sometimes reviewers rope in Ellipsis by asking questions (we also support natural language Q&A about a PR) or by having a design discussion via GH comments and then assigning the change to Ellipsis
Only if they're already below average.
Interesting. Got any numbers how it affects team velocity?
But we know we need hard numbers, so we’re working on it. We don’t want to sell a novelty, the product needs to actually save time