This page is about the Code Review feature available for GitHub Pull Requests.
This feature requires to have the GitHub App installed and works only for users with the GitHub App.
The feature works as is:
- Developers send a Pull Request on GitHub
- Pull Requests is being inspected by Code Inspector.
- The Code Review is being added as a check
- Any subsequent commits from developers on the code review are being inspected as well.
Note that any commit on the pull request will trigger a new analysis. Each Analysis is between the base commit of the pull request and the latest commit at the time of analysis.
The request of the Code Review is shown on the Pull Request (as shown below). You notice three sections:
- Code Inspector - Pull Request Code Review: this is the code review part, that interests you!
- code-inspector/violations: this gives a simple signal if this pull request introduce more violations (useful to automate merge based on the number of introduced violations)
- code-inspector/duplicates: this gives a simple signal if this pull request introduce more duplicates (useful to automate merge based on the number of introduced duplicates)
You can also see the errors surfaced for each file. For each error reported, our engine surfaces:
- severity: is that an important issue?
- category: what type of issues is it? (e.g. documentation, security, safety, etc.)
- description: a short description of what the problem is.
Sometimes, some errors surfaced by code analysis are not relevant (such as code-style). You can ignore some rules reported by our engines. Ignored rule will be ignored for the next analysis but also for any analysis on our platform.
To ignore a violation, go on the resolve link on the Pull Request (as shown above). That will connect you on a page on code-inspector (make sure you are logged on the website). Just click on the Ignore button on that interface to ignore a violation. Next analyses and code reviews will not include this rule.
If you have any question regarding the migration (or any other topic), please contact us.