forked from github/safe-settings
-
Notifications
You must be signed in to change notification settings - Fork 0
/
suborg.yml
184 lines (153 loc) · 7.21 KB
/
suborg.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
# This settings can be used to create suborg level settings
# List of repos that belong to the suborg
suborgrepos:
- test*
# You can use Glob patterns
suborgteams:
- core
#repository:
# This is the settings that need to be applied to all repositories in the org
# See https://developer.github.com/v3/repos/#edit for all available settings for a repository
# A short description of the repository that will show up on GitHub
#description: description of the repo
# A URL with more information about the repository
#homepage: https://example.github.io/
# Keep this as true for most cases
# A lot of the policies below cannot be implemented on bare repos
# Pass true to create an initial commit with empty README.
#auto_init: true
# A comma-separated list of topics to set on the repository
#topics:
#- github
#- safe-settings
#- new-topic
#- another-topic
#- topic-12
# Either `true` to make the repository private, or `false` to make it public.
# If this value is changed and if Org members cannot change the visibility of repos
# it would result in an error when updating a repo
#private: false
# Can be public or private. If your organization is associated with an enterprise account using
# GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+, visibility can also be internal.
#visibility: private
# Either `true` to enable issues for this repository, `false` to disable them.
#has_issues: true
# Either `true` to enable projects for this repository, or `false` to disable them.
# If projects are disabled for the organization, passing `true` will cause an API error.
#has_projects: true
# Either `true` to enable the wiki for this repository, `false` to disable it.
#has_wiki: true
# The default branch for this repository.
#default_branch: main
# Desired language or platform [.gitignore template](https://github.com/github/gitignore)
# to apply. Use the name of the template without the extension.
# For example, "Haskell".
#gitignore_template: node
# Choose an [open source license template](https://choosealicense.com/)
# that best suits your needs, and then use the
# [license keyword](https://help.github.com/articles/licensing-a-repository/#searching-github-by-license-type)
# as the `license_template` string. For example, "mit" or "mpl-2.0".
#license_template: mit
# Either `true` to allow squash-merging pull requests, or `false` to prevent
# squash-merging.
#allow_squash_merge: true
# Either `true` to allow merging pull requests with a merge commit, or `false`
# to prevent merging pull requests with merge commits.
#allow_merge_commit: true
# Either `true` to allow rebase-merging pull requests, or `false` to prevent
# rebase-merging.
#allow_rebase_merge: true
# Either `true` to allow auto-merge on pull requests,
# or `false` to disallow auto-merge.
# Default: `false`
#allow_auto_merge: true
# Either `true` to allow automatically deleting head branches
# when pull requests are merged, or `false` to prevent automatic deletion.
# Default: `false`
#delete_branch_on_merge: true
# The following attributes are applied to any repo within the org
# So if a repo is not listed above is created or edited
# The app will apply the following settings to it
#labels:
# Labels: define labels for Issues and Pull Requests
#- name: bug
# color: CC0000
# description: An issue with the system
#- name: feature
# If including a `#`, make sure to wrap it with quotes!
# color: '#336699'
# description: New functionality.
#- name: first-timers-only
# include the old name to rename an existing label
# oldname: Help Wanted
# color: '#326699'
#- name: new-label
# include the old name to rename an existing label
# oldname: Help Wanted
# color: '#326699'
#collaborators:
# Collaborators: give specific users access to any repository.
# See https://developer.github.com/v3/repos/collaborators/#add-user-as-a-collaborator for available options
#- username: drstrange
# permission: push
# The permission to grant the collaborator. Can be one of:
# * `pull` - can pull, but not push to or administer this repository.
# * `push` - can pull and push, but not administer this repository.
# * `admin` - can pull, push and administer this repository.
#- username: beetlejuice
# permission: pull
# exclude:
# - actions-demo
# You can exclude a list of repos for this collaborator and all repos except these repos would have this collaborator
#- username: thor
# permission: push
# include:
# - actions-demo
# - another-repo
# You can include a list of repos for this collaborator and only those repos would have this collaborator
# See https://developer.github.com/v3/teams/#add-or-update-team-repository for available options
#teams:
# - name: core
# The permission to grant the team. Can be one of:
# * `pull` - can pull, but not push to or administer this repository.
# * `push` - can pull and push, but not administer this repository.
# * `admin` - can pull, push and administer this repository.
# permission: admin
# - name: docs
# permission: push
# exclude:
# - actions-demo
# You can exclude a list of repos for this collaborator and all repos except these repos would have this collaborator
#branches:
# If the name of the branch value is specified as `default`, then the app will create a branch protection rule to apply against the default branch in the repo
# - name: default
# https://developer.github.com/v3/repos/branches/#update-branch-protection
# Branch Protection settings. Set to null to disable
# protection:
# Required. Require at least one approving review on a pull request, before merging. Set to null to disable.
# required_pull_request_reviews:
# The number of approvals required. (1-6)
# required_approving_review_count: 1
# Dismiss approved reviews automatically when a new commit is pushed.
# dismiss_stale_reviews: true
# Blocks merge until code owners have reviewed.
# require_code_owner_reviews: true
# Specify which users and teams can dismiss pull request reviews. Pass an empty dismissal_restrictions object to disable. User and team dismissal_restrictions are only available for organization-owned repositories. Omit this parameter for personal repositories.
# dismissal_restrictions:
# users: []
# teams: []
# Required. Require status checks to pass before merging. Set to null to disable
# required_status_checks:
# Required. Require branches to be up to date before merging.
# strict: true
# Required. The list of status checks to require in order to merge into this branch
# contexts: []
# Required. Enforce all configured restrictions for administrators. Set to true to enforce required status checks for repository administrators. Set to null to disable.
# enforce_admins: true
# Required. Restrict who can push to this branch. Team and user restrictions are only available for organization-owned repositories. Set to null to disable.
# restrictions:
# apps: []
# users: []
# teams: []
#validator:
#pattern: '[a-zA-Z0-9_-]+_[a-zA-Z0-9_-]+.*'