As a side note, I understand why Gitea and Forgejo went for a “copy GitHub Actions” approach to their CI, but man do I wish more self-hosted repo software tried to copy Drone/Woodpecker instead. Iterative containers in the pipeline is such a smoother build experience, and it kind of sucks that Gitness is the only one doing it (that I know of).
They were still pulling in mainline Gitea changes while introducing their own stuff last I checked.
Pulling in mainline gitea changes, I did see. But I didn’t see any notable differences from gitea. Do you know of any?
Nothing concrete from what I can tell. Becoming a hard fork is relatively recent though (mid-November of last year, roughly).
As a side note, I understand why Gitea and Forgejo went for a “copy GitHub Actions” approach to their CI, but man do I wish more self-hosted repo software tried to copy Drone/Woodpecker instead. Iterative containers in the pipeline is such a smoother build experience, and it kind of sucks that Gitness is the only one doing it (that I know of).
Last time I checked they were working on forgejo runners / actions!