Discussion
I'm trying to move my website from GitLab to @Codeberg and ngl a bit overwhelmed with trying to figure out how the CI works for git-pages.
Can I use the CI or do I need to register before hand (I'm getting mixed signals) Is there a CI validation file somewhere so that I don't try to debug CI by just smashing it? Is there a cache for my PHP dependencies? How do I know all the extensions I need are in the 8.5-cli image? Yes I have a custom whacky static site generator, but it is my playground.
@Codeberg I did find that action, good to know I can just use it. Can I also use an image with it that included PHP or is that something that would require Woodpecker?
@Girgias yes, you can use different images in different steps of the pipeline, https://codeberg.org/git-pages/action has examples of that, using eg `actions/checkout@v7` for the cloning of the repo and then `actions/git-pages@v2` for the deployment of the output. You can similarly put an in-between action with a container of your choice for the actual build. ~b
Install Fedizen
Get the full app experience
@Girgias We offer two CI setups. Forgejo actions (which is open to all users out of the box) and Woodpecker (which requires requesting access). https://docs.codeberg.org/ci/
If you plan on using Forgejo Actions, there is a ready-to-use action to help you get started: https://codeberg.org/git-pages/action
action
Working with Codeberg's CI | Codeberg Documentation