Mohammed Naser 087801d6b3 Use load-branch with trusted repository ... When loading dynamic project data out of a trusted repository, we are defaulting to automatically selecting master as a branch to load from instead of the load-branch option that can be specified. This leads to a blind spot when verifying changes to zuul config on that repo. Change-Id: I766f455220b15f56480304bd5b72560733ece8be Co-Authored-By: Tobias Henkel <tobias.henkel@bmw.de>		2020-11-11 17:16:09 +01:00
..
git	Use load-branch with trusted repository	2020-11-11 17:16:09 +01:00
ansible-version.yaml	Make ansible version configurable	2019-03-15 09:09:16 +01:00
authorizations-templating.yaml	Authorization rules: add templating	2020-02-21 09:37:35 +00:00
authorizations.yaml	Add Authorization Rules configuration	2019-07-30 15:32:15 +00:00
branch.yaml	Add load-branch to tenant configuration	2020-02-13 11:31:01 +01:00
exclude-all.yaml	Don't exclude config if excluded in earlier tenant	2019-02-11 16:03:57 +01:00
extra.yaml	Fix multi-tenant caching of extra config files	2019-07-03 18:43:37 -07:00
groups.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
groups2.yaml	Don't validate references for excluded config items	2018-05-03 09:58:02 +02:00
groups3.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
groups4.yaml	Do not call merger:cat when all config items are excluded	2018-02-07 12:12:25 +01:00
groups5.yaml	configloader: skip merger:cat when no items are included	2018-06-18 05:47:46 +00:00
invalid.yaml	Add tenant yaml validation option to zuul client	2018-07-23 17:00:57 +02:00
override.yaml	Test coverage to exclude pipeline with untrusted project	2019-01-20 13:34:37 -05:00
simple.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
tenant_config_script.py	Tenant config can be read from an external script	2018-04-03 14:33:41 +02:00
unprotected-branches.yaml	Optionally limit github to protected branches	2017-08-03 11:50:26 +02:00