[
https://issues.apache.org/jira/browse/FLINK-34330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813547#comment-17813547
]
Matthias Pohl commented on FLINK-34330:
---------------------------------------
Interesting, thanks for the pointer. I came up with it because Apache Arrow has
a
[apache/arrow:.github/CODEOWNERS|https://github.com/apache/arrow/blob/main/.github/CODEOWNERS]
configuration file for exactly that purpose. I also found [Apache
Geode|https://cwiki.apache.org/confluence/display/GEODE/Introduce+Codeowners+file]
using this functionality. They are referring back to the {{.asf.yml}} which
allows branch protection and automatic assignment for reviews (see [.asf.yml
docs|https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Branchprotection]).
So, maybe that policy changed or was relaxed?
> Specify code owners for .github/workflows folder
> ------------------------------------------------
>
> Key: FLINK-34330
> URL: https://issues.apache.org/jira/browse/FLINK-34330
> Project: Flink
> Issue Type: Sub-task
> Affects Versions: 1.19.0, 1.18.1
> Reporter: Matthias Pohl
> Priority: Major
>
> Currently, the workflow files can be modified by any committer. We have to
> discuss whether we want to limit access to the PMC (or a subset of it) here.
> That might be a means to protect self-hosted runners.
> See the [codeowner
> documentation|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners]
> for further details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
