[
https://issues.apache.org/jira/browse/HDDS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951269#comment-17951269
]
Attila Doroszlai commented on HDDS-12999:
-----------------------------------------
bq. t probably is better not to trigger any actions for pushing commits to a
fork branch. Developers may push incomplete work.
On the contrary, it is best to trigger actions in forks to give developers
feedback about their work before opening PRs, where the workflow consumes
Apache shared resources. Developers can cancel workflows (in their forks)
they are not interested in.
bq. When it is ready, we can trigger it manually.
We cannot have "pending" workflow in forks. It is either triggered or not.
Developers won't trigger workflows manually.
> Sync fork should not trigger GitHub action
> ------------------------------------------
>
> Key: HDDS-12999
> URL: https://issues.apache.org/jira/browse/HDDS-12999
> Project: Apache Ozone
> Issue Type: Improvement
> Components: build
> Reporter: Tsz-wo Sze
> Priority: Major
> Attachments: image-2025-05-08-12-35-11-264.png
>
>
> Currently, if I sync my Ozone fork with the apache/ozone, it will trigger a
> GitHub action. It sometimes trigger more than one actions; see the
> screenshot below. Let don't trigger it for saving resources.
> !image-2025-05-08-12-35-11-264.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
