[Jenkins-infra] Should we use setting app on github?
Olblak
me at olblak.com
Wed Oct 23 07:14:07 UTC 2019
Hi Everybody,
Halkeye recently transferred jenkins-wiki-exporter <https://github.com/jenkins-infra/jenkins-wiki-exporter> to the jenkins-infra organization on GitHub and also requested at the same time to use the setting app <https://probot.github.io/apps/settings/> which in short allow to configure a github repository from a .github/settings.yml
For now I temporarily approved the request for that repository *only*, as I think it can bring visibility.
On the other side, it also means that everybody who has write permission to that repository can change the settings, so the admin permission becomes useless.
Secondly since I don't expect those configuration to change really often, considering that everything is public by default, I am not sure to see the added value, excepted allowing everybody to audit the change through the git history.
Finally to me most important repository information for contributors is provided by the CODEOWNER with more granularity basically who's responsible for a specific part of a repository.
So I am gathering your feedback here, should we consider this app non relevant for the jenkins-infra organisation or should we generalize it?
Ps: Halkeye also configure specific labels in his repository which I think should be configured as default labels at the organization level so for every repositories as defined here <https://github.com/jenkins-infra/jenkins-wiki-exporter/blob/master/.github/settings.yml#L70-L14>
Olivier
---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20191023/772f3bdf/attachment-0001.html>
More information about the Jenkins-infra
mailing list