You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+51-49Lines changed: 51 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,19 +9,20 @@
9
9
> It is possible to override this behavior and specify a custom repo instead of the `admin` repo.<br>
10
10
> This could be done by setting an `env` variable called `ADMIN_REPO`.
11
11
12
-
1. In `safe-settings` the settings can have 2 types of targets:
12
+
1. The **settings** in the **default** branch is applied. If the settings are changed in a non-default branch and a PR is created to merge the changes, it would be run in a `dry-run` mode to evaluate and validate the settings, and checks would pass or fail based on that.
13
+
2. In `safe-settings` the settings can have 2 types of targets:
13
14
1.`org` - These settings are applied to the `org`. `Org`-targeted settings are defined in `.github/settings.yml` . Currently, only `rulesets` are supported as `org`-targeted settings.
14
15
2.`repo` - These settings are applied to `repos`
15
16
16
-
2. For The `repo`-targeted settings there can be at 3 levels at which the settings could be managed:
17
+
3. For The `repo`-targeted settings there can be at 3 levels at which the settings could be managed:
17
18
1. Org-level settings are defined in `.github/settings.yml`
18
19
> **Note**
19
20
> It is possible to override this behavior and specify a different filename for the `settings` yml repo.<br>
20
21
> This could be done by setting an `env` variable called `SETTINGS_FILE_PATH`.
21
22
22
23
2.`Suborg` level settings. A `suborg` is an arbitrary collection of repos belonging to projects, business units, or teams. The `suborg` settings reside in a yaml file for each `suborg` in the `.github/suborgs` folder.
23
24
3.`Repo` level settings. They reside in a repo specific yaml in `.github/repos` folder
24
-
3. It is recommended to break the settings into org-level, suborg-level, and repo-level units. This will allow different teams to define and manage policies for their specific projects or business units. With `CODEOWNERS`, this will allow different people to be responsible for approving changes in different projects.
25
+
4. It is recommended to break the settings into org-level, suborg-level, and repo-level units. This will allow different teams to define and manage policies for their specific projects or business units. With `CODEOWNERS`, this will allow different people to be responsible for approving changes in different projects.
25
26
26
27
> **Note**
27
28
> `Suborg` and `Repo` level settings directory structure cannot be customized.
0 commit comments