#forgejoactions — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #forgejoactions, aggregated by home.social.
-
Forgejo Runner, the program executing workflows of continuous integration in #Forgejo, has been released in version 13.0. It comes with breaking changes that may break current workflows for Forgejo Actions users. These changes improve security, predictability, and maintainability. https://forgejo.org/2026-08-runner-release-v13/
-
Kennt jemand noch eine gute Doku oder ein Tutorial zum Deployment von Webseiten von git zu Stage oder Live?
-
Temos um sistema de gerenciamento financeiro e de pessoas associadas feito do zero. Até ontem, todo desenvolvimento e tarefas de gerenciamento estavam no Github. A partir de hoje estamos usando uma instalação própria do #Forgejo e para rodar as tarefas recorrentes (CI, etc.) o #ForgejoActions em uma VM rodando dentro do hackerspace!
Para quem quiser dar uma olhada no código:
https://forja.lhc.net.br/LHC/thebook -
Help appreciated: Is there a way to delete old workflow runs in Forgejo?
I mistakenly pushed all tags that I previously deleted via the API, so I now have ~300 failed workflows from tonight (that I got somehow stopped) ...
(Deleted the tags both on origin and locally this time ...)
#forgejo #forgejoactions #git -
I stayed up way too later to finish this :a2bsleepy:
https://firq.dev/blog/deploying-this-round-3 #blog #rssfeed #astro #forgejoactions #cicd -
RE: https://social.treehouse.systems/@whitequark/116454915873481567
Anyone publishing a Quarto blog with Codeberg Pages? I'm new to this automation stuff, and can't decide between WebHooks, Forgejo Actions, and WoodPecker CI. If I use actions or WoodPecker, it would be just for "quarto render"; any R code output is frozen and will be run on my own computer. I have a custom domain.
#QuartoPub #CodebergPages #GitPages #ForgejoActions #WoodPeckerCI
-
Anyone know of a guide on how to migrate a Build Awesome (11ty) site to Forgejo from GitHub? I somehow got stuck on the SSH auth setup last I tried 😭 I may just need to try again with fresh eyes.
I've been deploying to Neocities with GitHub Actions thanks to @sophie's great guide. I'm sure Forgejo actions will also be a sticking point so any tips here would be awesome. https://localghost.dev/blog/how-i-deploy-my-eleventy-site-to-neocities/
-
It seems that whenever I look more closely at what #github does, it blows my mind. I had no idea that the actions/checkout which everyone seems to be using to basically run "git clone" is 38k LOC of pure node.js madness.
How about we use 9 lines of shell instead?👋 @adyxax
-
Ach, so ein tolles Gefühl, habe nach langer Zeit mal wieder die VM mit dem Forgejo Runer hochgefahren, ein neuen git Tag der aktuellen caddy Version gepusht, schon läuft die Kiste los und baut einen caddy Conatiner mit dem Hetzner DNS Provide Modul. 💓
Nach 3-4 Minuten habe ich also ein neues Image im Codeberg Image Repository =) -
After read the #forgejo documentation I build my first #forgejoActions
I like that the forgejo actios are similar to the github action.
https://codeberg.org/codeDude/romodoro-socket/pulls/5/files -
My first #ForgejoActions running on #codeberg
Note: I'm using the images that codeberg offer
-
Which container images is everbody using for running Nix related jobs in Forgejo Actions?
I cobbled together some container images which include Node.js for running most unmodified upstream actions, but I'm wondering if I just missed some great pre-existing ones.
-
So I'm trying to use Forgejo Actions. I defined a job to run inside a OCI container that has the build tool I need. The Action to checkout the repository does not work because it expects nodejs to exist in that container? Also can't share the file system between jobs. Also can't install nodejs in that build container because it doesn't include a package manager (which is fine normally).
I've seen some comments that recommend to build and publish a custom container that includes both the tool I need and nodejs, but surely that can't be the solution.
I don't understand how this is supposed to work? If someone knows how this Action system is intended to be used I'd be grateful.
-
I’m very interested in moving my 11ty deployment from GitHub to the omg.lol SourceTube (M$ and AI etc🤮).
It seems like I’d mainly need to figure out the Actions Runner to build and publish to my host NeoCities.
-
In an EPIC bout of yak-shaving I have reduced the build time for this static site infrastructure running on a puny VPS by a factor of 5. Come along on this undiagnosed journey.
Anatomy of a yak-shave:
- See what had happened was...
- I wanted to put animated snowflakes on my site
- Learned about CSS animation, nice
- Learned how to not bork screen readers
- Remembered I barely got my CI/CD working with Forgejo runner
- Remembered it takes for ever to deploy
- Realized most of it is just downloading and setting up dependencies
- How hard can it be to bake all that into my own image?
- Oh Forgejo supports a container registry too, nice!
- If I can't quickly build and push an image then this will have to wait
- Oh wow, that was really easy
- False sense of how well things are going
- All the freaking examples are for using public forges with public container registries
- Fall down several totally wrong rabbit holes due to lack of knowledge
- Have not stood up, eaten, drank, blinked in hours by this point
- Things are kinda working, yay! Noooo version mismatch
- I barely know Nix flakes, how do channels work, how do you pin them?
- Realized my tools have been broken but flake.lock has been saving me, nice!
- Fatigue related silly errors and utter faith this attempt will work so I don't need to make a quick test setup and test on a much faster setup
- Revert back to how it was, drink water, oh wait silly me...
- Victory
- Should probably write a blog post, it'll be SO fast to deploy
-
Our hosted #ForgejoActions now have a `medium` runner available with 10 minutes timeout. Take a look at the announcement: https://codeberg.org/actions/meta/issues/3#issuecomment-8339199
Hosted Forgejo Actions is our second hosted CI/CD next to the existing #WoodpeckerCI which already has more generous limits.
-
Developers self hosting their Forgejo instances, or using another instance and need to setup an actions runner may find this new blog post useful :blobcatderpy:
We setup a forgejo runner with rootless podman in fedora!
https://blog.hachem.dev/setting-up-forgejo-runner-in-a-fedora-server-with-rootless-podman/
-
Finally migrated my personal website (powered by #HugoSSG) from #GitLab to #Codeberg. Including #CI via #ForgejoActions and hosting via #CodebergPages. Jobs are running on the local #homelab server.
There are jobs for building and deploying the website and for updating the contribution data through #contripy.
So far this has been very smooth and straightforward. Though I still need to learn the new CI workflow syntax as I'm used to GitLab from the daytime job.
-
After yesterday's success of setting up a Foregejo Runner with Codeberg the problems started.
I'm working on a Local Action to upload files to FTP. It consists of action.yml, Dockerfile and entrypoint.sh but no change to any of these files triggers a rebuild of the Image. So, I'm stuck with the first built Image version, unless I shell into the Docker-in-Docker container and remove the Image manually.
This feels like either a caching issue or I am missing something obvious.
-
I added second #adguard node that shares the same codebase, but I wanted to have only one codebase (not just copied), so I set CI/CD workflow using #ForgejoActions on @Codeberg