Hey folks, Seeing the merge window configs rolling in along with people starting to open GitLab merge requests rather than exclusively emailing patches, I have a suggestion to make everyone's lives a bit easier, especially with the configurations: Start making use of the "developer" role[0] in GitLab. I recommend reading over the permissions to get an idea of what's allowed, but the short of it is developers can't push to protected branches, so can't accidentally (or maliciously) change any of the important branches in the repository, but they *can* modify non-protected branches like the config branches[1], apply labels, and so on. Rather than having a script set the configs, then someone review them, ask the maintainer to change it, then review it again, then have the maintainer merge it, you can just check out the config branch for the merge request, change it yourself, push it, and mark it ready (or get more reviews) for merging. This cuts down on a lot of back and forth so it'll save everyone time. [0] https://gitlab.com/help/user/permissions [1] https://gitlab.com/cki-project/kernel-ark/-/branches/all?utf8=%E2%9C%93&search=configs%2F - Jeremy _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
