Neo | DocsAdd as a reviewer
To get Neo to review a PR, add Neo as a reviewer in your code repository tool.
Neo will leave a comment saying it has started reviewing, and another when it has finished. If Neo has no comments on your PR, it will approve it!
🪣 In BitBucket, as well as assigning the PR to Neo, it must be marked as “Ready for review”. This is the way BitBucket handles draft PRs and reviews.
You can also get Neo to perform a review by leaving a comment on the PR asking. For example say “@neo review this”. This is the only way of getting Neo to review its own PRs on GitHub.
What Neo reviews
-
General reviewer - general review of common issues relevant to any team
-
Semantic linter - customise Neo with your team’s rules. Recommended!
-
One-off custom reviews - give one off criteria for a special review. Neo will confirm what it has reviewed.
Get Neo to fix what it reports
You can get Neo to implement changes it has suggested on a PR. Just reply to Neo’s review comments telling it to, e.g. “@neo fix it”. See Comment on a PR for more.
Bulk fixes
A common pattern is to have Neo or a colleague give you a comment in a pull request, and reply with something like “@neo, fix it!”. Neo has all of the context it needs so you don’t need to explain further.
Sometimes you have received the same or similar comment several times in your PR, and Neo gives you the convenience to address them all at the same time. You can say thing like:
-
@neo fix all of your comments
-
@neo fix all comments to do with catching generic Exceptions
-
@neo fix all comments about typos
Suggestions
If a change is short, Neo will make a suggestion you can accept with one click.