3 ms·

Quick note that the forked project doesn't have the CI feature released in 1.9, which is the primary subject of this thread.

• dave78 4y ago
  I assume they will follow up with their own 1.19 release soon. The blog below indicates they will have the CI feature. https://forgejo.org/2023-02-27-forgejo-actions/ https://forgejo.org/2023-02-27-forgejo-actions/
  • joencott 4y ago
    It is sad to see that the forgejo team accept and promote the built-in CI server. When the PR was first made they said they shouldn't trust the code, and will stick with woodpecker.
  • remram 4y ago
    It seems that they have "soft forked" act as well. I worry that they will spend more time maintaining all their forks than doing any original development...
    • dave78 4y ago
      Gitea soft forked act as well, from https://gitea.com/gitea/act https://gitea.com/gitea/act: "This is a custom fork of nektos/act, for the purpose of serving act_runner. It cannot be used as command line tool anymore, but only as a library. It's a soft fork, which means that it will tracking the latest release of nektos/act."
      • remram 4y ago
        I see, removed that from my comment then, sorry. I looked at their go.mod and assumed. Now I worry even more about everyone maintaining forks of everything rather than doing original development. I wonder what differences there are between Gitea's and Forgejo's forks, and also why they couldn't work with upstream.