Could this be due to the red x indicating a problem which then tells .asf.yaml to stop?
> On Feb 5, 2021, at 10:43 AM, Tobias Bouschen > <tobias.bousc...@googlemail.com.INVALID> wrote: > > The website does not update for me as well. > > The changes were successfully deployed to the 'publish' branch, so my > guess is that the issue again lies with the hosting backend. I am going > to post another comment to the INFRA jira. > > On 05/02/2021 19:31, Craig Russell wrote: >> I'm still not seeing the changes to get-involved. >> >> Anyone else seeing the new content? >> >> Craig >> >>> On Feb 4, 2021, at 2:42 PM, Craig Russell <apache....@gmail.com> wrote: >>> >>> I still have not seen these changes to get-involved published to the live >>> site. >>> >>> Are we still suffering from "JDO Site Failed To Deploy"? >>> >>> Craig >>> >>>> On Feb 4, 2021, at 12:06 PM, tilma...@apache.org wrote: >>>> >>>> This is an automated email from the ASF dual-hosted git repository. >>>> >>>> tilmannz pushed a change to branch master >>>> in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git. >>>> >>>> >>>> from dddc5e4 Remove 'docs/' and 'content' >>>> add 64e90c7 Update get-involved.adoc (#22) >>>> >>>> No new revisions were added by this update. >>>> >>>> Summary of changes: >>>> src/main/asciidoc/get-involved.adoc | 13 ++++++------- >>>> 1 file changed, 6 insertions(+), 7 deletions(-) >>>> >>> >>> Craig L Russell >>> c...@apache.org >>> >> >> Craig L Russell >> c...@apache.org >> Craig L Russell c...@apache.org
