When commit checks are enabled, P42+ analyzes and verifies code changes in the repository whenever:
- Pull requests are opened, or
- Commits are made to the default branch of the GitHub repository.
Pull Request Checks
If the commit checks setting is enabled for a code action, P42+ performs code analysis whenever pull requests are made to the repository.
📝 P42+ checks are only performed on files that are included in the pull request.
To check the status for pull request checks:
- Navigate to the pull request page for your GitHub repository. For example, go
- Click on the check status indicator next to your pull request title.
- In the commit checks summary, click on Details to view the check details page for more information on each P42+ analysis check.
Default Branch Checks
If the commit checks setting is enabled for a code action, P42+ performs the code analysis whenever commits are made to the default branch of the repository.
To check the status for commit checks:
- Navigate to your GitHub repository. For example, go to
Click on the check status indicator next to your commit hash. You should see a P42+ Code Analysis entry in the popup.
In the commit checks popup, click on Details in the P42+ entry to view the checks details page for more information on each P42+ analysis check.
You can find the following information in the GitHub checks page for your repository:
Number of Suggestions Count of how many suggestions have been found.
List of P42+ checks with status The list of P42+ analysis types where the commit checks is enabled. For each type, a pass/fail indicator is shown.
Suggestions The details section lists all files in the commit which failed the P42+ commit check, and provides a simplified diff view on the P42+-suggested changes for each file.
Re-run check It may be useful to re-run the P42+ check when any repository settings are changed. For example, if