Repository settings

Changing a repository's settings is an admin task. Open a repository from Repositories to get here.

#What Default means

Most controls open on Default, and the label tells you which workspace value they are following, so Default · Medium means this repository is on Medium because Review config says so.

Pick any other value and this repository stops following the workspace for that one setting. Everything else keeps inheriting. Choose Default again to hand it back.

#Review behavior

The Review behavior card carries the same controls as the workspace page, so Severity threshold, Reviews post as, Merge gate and Sandbox tests in the gate all mean what they mean on Review config.

The four per-review switches are here too: Walkthrough pages, Sandbox test runs, Browser integration tests and Static analysis. So is Auto-fix, which is set per repository, so this is the page where you turn it on. See Auto-fix pull requests.

#Instructions and ignored paths add up

Repository instructions and Ignored paths behave differently from the rest. Rather than replacing the workspace values, they are added to them, so a review of this repository gets both sets.

That is why the ignored-path chips you inherit are shown dashed, and why the instructions card offers to show the workspace instructions still in effect. Both are there so you can see what you are adding to.

Repository instructions are the right place for anything true of this codebase and nothing else: a framework version, a migration in progress, a directory that looks abandoned and is not.

#The tools that belong to a repository

Three cards further down are about this repository specifically rather than about how it is reviewed.

The in-repo config card sits alongside them, showing whether this repository carries an .inline.yml and what inline made of it. See In-repo config.

Choose Save settings when you are done. The next review of this repository uses what you set.