Hello Apratim, Good move!
Please note that if you are using Hugo, Jekyll, or Pelican systems for your website, you don't have to utilize Github actions for publishing it. Relevant links: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories You can also look at this website (for Jekyll): https://github.com/apache/privacy-website With every commit, the build system is triggered, pushing the outcome to the asf-staging branch. From there, it is visible on a staging website. Once merged to asf-site, it will appear on the main website. If you want support with that kind of building, I gladly help - at least for Jekyll sites :) Kind regards, Christian On Fri, Mar 1, 2024, at 19:27, Apratim Shukla wrote: > Greetings, > > I hope all is well. I'm reaching out to request your support for a critical > update to the ResilientDB project, detailed in JIRA ticket INFRA-25571 > <https://issues.apache.org/jira/browse/INFRA-25571>. We aim to transfer the > ResilientDB Homepage repository ( > https://github.com/ResilientEcosystem/resilientdb.github.io/) to Apache's > GitHub organization for automated deployment via GitHub Actions. This > transition is vital for enhancing the project's CI/CD processes and overall > visibility. > > *Objective: *Transfer the repository to enable automated deployments. > *Benefit:* Streamlines updates, reduces manual effort, and increases > project visibility. > *JIRA Ticket:* INFRA-25571 > <https://issues.apache.org/jira/browse/INFRA-25571> > > We appreciate any guidance or support you can provide to facilitate this > transition. Thank you for your time and consideration. > > Best regards, > Apratim
