Between Forgejo, Gitea, Gitlab etc., which do you prefer and why?
from otter@lemmy.ca to nostupidquestions@lemmy.world on 19 Sep 08:39
https://lemmy.ca/post/51882577

If possible, also mention what the use case is (ex. Contributing to a project, hosting your code privately, workplace, etc.)

Edit: Removed Codeberg from the post title as I mixed things up

#nostupidquestions

threaded - newest

CameronDev@programming.dev on 19 Sep 08:51 next collapse

Gitlab. Was on gitea, but it lacked CI integration (not sure if that has changed) and generally felt less polished. Gitlab is used at work, so its nice having something familiar.

hddsx@lemmy.ca on 19 Sep 11:34 collapse

Funny, I switched to Forgejo because Gitlab stopped running smoothly in four years between trials. I don’t understand why it’s such a hog

CameronDev@programming.dev on 19 Sep 12:42 next collapse

It is a bit of a hog at times. But it hasnt been bad enough for me to switch. Does forgejo do CI?

felbane@lemmy.world on 19 Sep 13:09 collapse

forgejo.org/docs/latest/user/actions/overview/

Actions supports using runners, and there are also webhooks that are useful for triggering e.g. Jenkins. I use the latter, works great.

foggy@lemmy.world on 19 Sep 15:35 collapse

Edit your configs.

It is a resource hog It you don’t tell it not to be. And for private use, you absolutely don’t need it to be.

sbeak@sopuli.xyz on 19 Sep 09:04 next collapse

Currently I use Codeberg and Forgejo. The former for cloud backup and the latter for local backup.

napkin2020@sh.itjust.works on 19 Sep 09:34 next collapse

Forgejo. Initially went with Gitea and made the switch because why not.

To me, everything works perfectly, from basic git stuff to CI. It was only for my hledger stuff since it’s way too sensitive to be on any other machine but mine, but now I use forgejo way more than GH.

KexPilot@lemmy.world on 19 Sep 09:47 next collapse

It’s my turn to do the obligatory mention of SourceHut :)

It is in alpha, but it is really promising. It is going all-in on email based git workflows (which was the original way of doing it before the github-style PR based workflow). I love the style and it’s minimalism - but don’t let that fool you, it has many features that you might not see at first glance. Imagine if cgit or gitweb was extended into a software forge with built-in support for email patches, mailing lists, issue tracking and CI.

If you are the type of person who attracts garbage issue tickets and often has to reject low-effort PRs on your projects, it forces a really good minimum entrance bar. Of course this comes at the cost of visibility of your projects, less networking effect, so I would suggest to not use it if you want easy visibility and 3rd party contribution on your projects.

asudox@lemmy.asudox.dev on 19 Sep 10:18 next collapse

Codeberg is an instance, not software. It runs on Forgejo.

Forgejo is a hard fork of Gitea.

So my answer is Forgejo.

otter@lemmy.ca on 19 Sep 15:18 collapse

Thanks, I’ve edited the title accordingly

slazer2au@lemmy.world on 19 Sep 10:53 next collapse

Work is gitlab, private is Forgejo.

varnia@lemmy.blahaj.zone on 19 Sep 11:08 next collapse

Forgejo as private instance, mirror important stuff to Codeberg. This way you can also restrict access to your private instance while have your code publicly available on Codeberg.

A_norny_mousse@feddit.org on 19 Sep 11:22 next collapse

Framagit uses Gitlab
Notabug uses gogs

y0kai@lemmy.dbzer0.com on 19 Sep 14:46 next collapse

I like codeberg simply because it is pronounceable.

philpo@feddit.org on 19 Sep 19:31 collapse

Gitea once now Forgejo.