Go ahead. We've been self-hosting Gitea with Drone/Woodpecker for years; either it or Forgejo will do fine if you're okay with their feature set. I sometimes wander into these GitHub threads to have a laugh; our Gitea instance has had several minutes of downtime combined over the last few years, all of them planned (to upgrade Gitea) and in the middle of the night.

▲

lioeters 2 days ago | parent | next [-]

Ooh, Woodpecker CI works with Gitea and Forgejo. https://woodpecker-ci.org/ That might be last piece I needed to migrating Git repos from GitHub to a self-hosted forge.

Edit: Actually there's Gitea Actions and Forgejo Actions, that might be enough for my use case.

https://docs.gitea.com/usage/actions/

https://forgejo.org/docs/next/user/actions/reference/

▲

dymk 2 days ago | parent [-]

I’ve found gitea actions (based on ACT, so it’s nearly identical to a GitHub action runner) to work great. Migrating a GitHub workflow is mostly just a file name change.

	▲	lioeters 2 days ago \| parent [-]
		Good to know!

▲

MiracleRabbit 2 days ago | parent | prev | next [-]

Gitea Upgrading.. replacing binary, restarting. I love it.

Same for Forgejo.

▲

scottyah 2 days ago | parent | prev [-]

I struggled with Woodpecker for a bit, but now gitea has Actions that work wonderfully for my use case (and one less tool to support). I believe they also highlight compatibility with a github action protocol of sorts. Might be worth looking into.