[
https://issues.apache.org/jira/browse/CALCITE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700235#comment-17700235
]
Stamatis Zampetakis commented on CALCITE-5584:
----------------------------------------------
To rectify the situation I forced pushed the main branch to the site branch
(there was only one commit difference) and manually deployed the website
([https://github.com/apache/calcite-site/commit/3997c714582c97bf22f98e3f7b902c70e0c28e07)]
by building the site locally.
> Publish website action only triggers for the last commit in the chain
> ----------------------------------------------------------------------
>
> Key: CALCITE-5584
> URL: https://issues.apache.org/jira/browse/CALCITE-5584
> Project: Calcite
> Issue Type: Bug
> Components: build
> Affects Versions: 1.34.0
> Reporter: Stamatis Zampetakis
> Priority: Major
>
> At some point, towards the end of the 1.34.0 release process, I pushed two
> commits together from my local repository to the remote:
> *
> [https://github.com/apache/calcite/commit/de305074f4dad5f157abb149319d1664fa2fe68d]
> *
> [https://github.com/apache/calcite/commit/421c871e5f9f3ea7c660bea48f2099d0cd41ffcf]
> The [publish website
> action|https://github.com/apache/calcite/actions/runs/4416430449/jobs/7740705842]
> was triggered only for the last commit,
> 421c871e5f9f3ea7c660bea48f2099d0cd41ffcf, which doesn't have any changes to
> the site thus the changes in de305074f4dad5f157abb149319d1664fa2fe68d are not
> reflected to calcite.apache.org.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
