Hi there, and thanks a lot for the awesome work on Codeberg and Codeberg-CI 😊.
After having the discussion in this issue of Codeberg pages about different ways of simplifying the deployment process for static Hugo websites, I made a script that mimicks the GitHub action for deploying Hugo pages to GitHub pages. I'd like to have a look if a similar CI pipeline can be achieved with Codeberg-CI.
Currently, one supported way of hosting Codeberg Pages is to have the Hugo-generated static files in a pages branch, which is what my script automates, and is analogous to what the GitHub action does for GitHub pages (on GitHub the branch is gh-pages). I was thus wondering if something similar could be done with Codeberg-CI, as it would be much more user-friendly than manually getting the static files to the pages branch, or having to use scripts to automate that.
I'd thus like to have a look at it, with my personal page with the repo here. I'd be glad to then have a look at updating the Codeberg pages documentation for simplifying the deployment of pages from static site generators.
LMK what you think, and thanks a lot!
<!-- Thank you for requesting access to the Codeberg CI.
Please make sure you read the READMe in the project root and understood
- the caveats for "as-is" CI access which might break
- the rules that apply for the usage
- how to apply
Thank you very much, please write below or remove this template. -->
Hi there, and thanks a lot for the awesome work on Codeberg and Codeberg-CI 😊.
After having the discussion in [this issue](https://codeberg.org/Codeberg/pages-server/issues/59) of Codeberg pages about different ways of simplifying the deployment process for static Hugo websites, I made a [script](https://codeberg.org/adam/website/src/branch/main/deploy.sh) that mimicks the GitHub action for deploying Hugo pages to GitHub pages. I'd like to have a look if a similar CI pipeline can be achieved with Codeberg-CI.
Currently, one supported way of hosting Codeberg Pages is to have the Hugo-generated static files in a `pages` branch, which is what my script automates, and is analogous to what the GitHub action does for GitHub pages (on GitHub the branch is `gh-pages`). I was thus wondering if something similar could be done with Codeberg-CI, as it would be much more user-friendly than manually getting the static files to the `pages` branch, or having to use scripts to automate that.
I'd thus like to have a look at it, with my personal page with the [repo here](https://codeberg.org/adam/website). I'd be glad to then have a look at updating the Codeberg pages documentation for simplifying the deployment of pages from static site generators.
LMK what you think, and thanks a lot!