Approval rules and branch policies at the organization level in SourceCraft
You can use a dedicated .sourcecraft repository to manage the general approval rules and branch policies for all repositories in an organization. This ensures uniform development standards and simplifies administration.
When you create the .sourcecraft repository, all its configuration files automatically apply to all repositories in the organization. You can make this repository private; the configurations will persist across all the organization’s repositories.
Configuration files
The .sourcecraft repository supports the following configuration files:
.sourcecraft/review.yaml: Approval rule settings..sourcecraft/branches.yaml: Branch protection policies.
The syntax of organization-level settings is identical to that of repository-level settings.
How configurations are applied
Configuration changes are applied immediately after they are committed to either main or master branch of the .sourcecraft repository. Changes in other branches are not applied, allowing you to work on configuration changes in separate branches.
Individual repositories can override organizational settings, but only to enforce stricter requirements. For example, if the organization level settings require two approvals for a pull request, a specific repository may increase this number to three approvals, but not reduce it to one.
If there are errors, the merge of branches is rejected with a detailed description of problems.