[
https://issues.apache.org/jira/browse/HDDS-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950502#comment-17950502
]
Attila Doroszlai commented on HDDS-12999:
-----------------------------------------
[~szetszwo], we may skip {{build-branch}} for {{master}} in fork. But
{{populate-cache}} (triggered if there are POM changes) is important, because
it creates the Maven cache that allows saving time for builds (on all branches,
not just {{master}}).
BTW, syncing fork is not necessary if {{master}} in local clone tracks (gets
updates from) {{apache}} upstream repo. The state of {{master}} in fork is not
important in this case. I usually sync my fork once a week, in the offpeak
hours (when I don't have any dev workflow to run), only to keep the cache
up-to-date.
> 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
