[
https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831665#comment-17831665
]
Matthias Pohl commented on FLINK-34953:
---------------------------------------
I guess we could do it. The [GitHub Actions
Policy|https://infra.apache.org/github-actions-policy.html] excludes
non-released artifacts like website from the restriction:
{quote}Automated services such as GitHub Actions (and Jenkins, BuildBot, etc.)
MAY work on website content and other non-released data such as documentation
and convenience binaries. Automated services MUST NOT push data to a repository
or branch that is subject to official release as a software package by the
project, unless the project secures specific prior authorization of the
workflow from Infrastructure.
{quote}
Not sure whether they updated that one recently. Or do you have another source
which is stricter, [~martijnvisser] ?
> Add github ci for flink-web to auto commit build files
> ------------------------------------------------------
>
> Key: FLINK-34953
> URL: https://issues.apache.org/jira/browse/FLINK-34953
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
> Reporter: Zhongqiang Gong
> Priority: Minor
> Labels: website
>
> Currently, https://github.com/apache/flink-web commit build files by local
> build. So I want use github ci to build docs and commit.
>
> Changes:
> * Add website build check for pr
> * Auto build and commit build files after pr was merged to `asf-site`
> * Optinal: this ci can triggered by manual
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
