Do no include Zuul conf from package repo
We do not expect to have Zuul load configuration elements from distgits repositories. If such repos contains a .zuul.yaml Zuul will not load it.
Build succeeded.
I missed WHY part in the commit message
rebased onto 55baddf1f58b7d33109801a68aad4867db4a5249
Metadata Update from @fbo: - Pull-request tagged with: gateit
Build succeeded (gate pipeline).
Pull-Request has been merged by zuul
@apevec yes it deserved a better commit message. I've updated it.
sorry for being dense, I still don't get it: why wouldn't some distgit have specific Zuul jobs if they wish?
We had bad experiences with some unexpected .zuul.yaml or .zuul.d in repositories branches especially on github when people open PR from local branches. With Github protected branch option that's no longer an issue now) but with Pagure we don't have this option.
So better to prevent Zuul to read its config from distgit by default. But obviously it makes sense to allow it when needed and as you can that's actionable by repository.
Do no include Zuul conf from package repo
We do not expect to have Zuul load configuration elements
from distgits repositories. If such repos contains a .zuul.yaml
Zuul will not load it.