4 ms·
They (Gitea) introduced actions. It is already included in the current releases, but codeberg might just not activate it. It works quite good, I actually wrote
by RamblingCTO 4y ago
They (Gitea) introduced actions. It is already included in the current releases, but codeberg might just not activate it. It works quite good, I actually wrote a gitea action already ("gitea-release-drafter").
- hakre 4y agoNice, perhaps is worth to invest into such kind of "fediverse" (using Codeberg with my own hosted action runners/boxes), I'd buy into that feature much faster than into any other (e.g. using Codeberg for PRs from proprietary hosted "Codeberg" instances).
- RamblingCTO 4y agoThere's also work on that ;) the dude doing most of the work moved to forgejo and some parts are already implemented but I'm not sure what the state is. I would also love to see federation, that's what would really be a github killer and drive this ecosystem forward imho. - https://github.com/go-gitea/gitea/issues/18240 https://github.com/go-gitea/gitea/issues/18240 - https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59
- kotatsuyaki 4y agoGlad to see new options. I wonder if Codeberg is going to enable actions, given that they’ve already setup an experimental instance of Woodpecker that can be requested [1] on a per-user basis. [1]: https://codeberg.org/Codeberg-CI/request-access https://codeberg.org/Codeberg-CI/request-access