Project settings are useful to define how Clayton connects to your repository and how it will trigger the code reviews on your code:
Go to your Clayton homepage
Click on your Project > Settings > Policies
Scanning
Set up scan policy and code review criteria for your project.
Define which kind of files to ignore during code reviews:
You can use regex to prevent entire folders or files respecting certain naming conventions to be scanned by Clayton.
β
βExamples:
src/ProjectName/classRoot.*
src/ProjectName/lib1/
src/ProjectName/folder1/*.xml
.*file_to_exclude.*
β
Team
Invite and manage your engineering team.
Team members can have two different roles: Developer and Project Lead. Please read our dedicated article to know more.
Version control
Setup how Clayton connects to version control and monitors activity.
1. Create a webhook in your VCS with one-click.
2. Define what type of feedback you want to use.
Multiple (according to the active skills) or single status checks
Pull request approvals/declines or just comments
Main branch configuration