Guides
Repository rules and privacy
Tell the agents how your product is tested and deployed, limit the size of a change, block paths, and keep your product's news private.
After this guide, the agents follow your repository's rules, and the news about your product says only what you want.
Who can do it: a workspace admin or owner, or a person who may change everything in that product. See Roles.
Where the settings are
- Open Settings → Products, and press Settings on the product's row.
- Privacy is in the middle of the page.
- Repository rules is inside Technical settings, at the end of the page. It is closed at first.
- After a change, press Save in the bar at the bottom of the window. Discard drops what you typed.
In a product with several repositories, the first three rules below are on each repository's row instead, under Repositories → Details.
Repository rules
CI workflow name
CI is the automatic tests and the deploy that run on GitHub. Type the exact name of the GitHub Actions workflow that runs on the main branch after a merge, such as "CI/CD Pipeline". The platform follows its deploy.
Deploy job name
The job in that workflow whose success means that your product runs the change, such as "Deploy to AWS Production". If you leave it empty, a green run on the main branch counts as the release.
Health URL
An https address that answers 200 when your product is healthy, such as https://example.com/healthz. Auto-merge checks it after each deploy it starts. Redirects and private addresses do not count. See Turn on Auto-merge.
Most files per change and most lines per change
Most files per change is the most files one change may touch: from 1 to 200. The default is 20.
Most lines per change is the most lines one change may add and remove together: from 10 to 10,000. The default is 600.
A change that is larger is not sent to GitHub. You then choose what happens. See Approve a suggestion.
Extra paths agents may never touch
Type one pattern per line. Each pattern is a regular expression, matched against the paths in your repository. For example, ^payments/stripe/ blocks every file in that folder.
Some paths are always blocked, in every product. The agents never change them:
- CI workflows, such as
.github/; - infrastructure and deploy files, such as
docker/,ops/andscripts/; - container files, such as
Dockerfileanddocker-compose; - the agents' own instructions:
.claude/,.agents/,CLAUDE.mdandAGENTS.md; - database migrations;
- secrets and environment files, such as
.env; - dependency files, such as
package.jsonandrequirements.txt; - git settings.
Privacy
The agents read data from your integrations, and they write reports. Before anything is stored or sent, the platform removes e-mail addresses, IP addresses, phone and card numbers, IBANs and keys from both.
E-mail domains to keep
Type your own domains, one per line, such as acme.com. Addresses at these domains stay in the reports. Every other address is removed.
A private product
Tick Private product. Telegram, Slack and the daily e-mail then say only that there is news, with the label of the suggestion, such as F12, and the number of its pull request. The content stays on the website.
What you see when it worked
The part you changed says Saved. If a value is wrong, the part says what is wrong, and nothing in it is saved.
More
- Product settings: every setting of a product.
- Instruction files: the files in your repository that the agents read.
- When something does not work.