Skip to main content

Trigger your first Clayton review

David Martin avatar
Written by David Martin
Updated today

With Clayton is now possible to trigger code reviews targeting specific Branches of your repo or specific Pull requests available for your project.

Code reviews can be triggered automatically via webhook events, or manually:

  1. Go to your Clayton homepage

  2. Click on your project

  3. Click on the Branches tab or Pull requests

  4. Click Scan

You will receive a notification once the scan is completed.

Review Report

Once the review is done, you will be able to see the results and check the issues Clayton may detect. Reports are split by policies that are configured on the project and include the full explanation and fix resources for every problem detected. It is also possible to search findings by rule, author, file, commit ID, commit comments, and more.

Icons and colour coding

Code review not passed. Blocker issues detected; fix required.

Code review passed, with warnings. Non-blocking issues detected. Fix suggested but not required.

Code review passed. No issues detected.

Branch Scan History

You can find the history for a specific branch by going to Home, then Project, and finally Branches. Once you've selected the branch you're interested in, you'll see trends organized by:

  • Revision

  • Commit date

  • Contributor

  • Outstanding issues

  • Clayton Score

Issue Detail View

When you click on a detected issue, you can:

  • See the code snippet that's affected.

  • Author

  • Open Git directly to the relevant revision.

  • Access the Timeline tab to find both the date the issue was introduced and when it was detected.

Always-on protection for your pull requests

Clayton automatically reviews every pull request to continuously monitor developments and ensure full compliance at all times.

Read more here to learn how Clayton helps you keep your code quality under control automatically enforcing standards across the entire delivery.

Did this answer your question?