[trialect]

Forgejo is great and all... up until you're trying to use your SSO with a user named 'admin':

https://codeberg.org/forgejo/forgejo/issues/8030

then it just looks like a bad joke with all the anime girls and everything else...

[quectophoton]

There are also some minor issues with composite actions and reusable workflows.

If I use composite actions, the logs get associated with the wrong step[1]. It's just a visual thing (the steps themselves run fine), but having 90% of your action logs in the "Complete job" step is unpleasant.

For reusable workflows there's a few open issues as well, but what happens in my case is that jobs just don't start at all, they stay as "Waiting" forever.

These issues only matter if you write your own reusable actions with YAML (the actions written in JavaScript seem to work fine), but it's worth mentioning.

Other than these two issues, I'm very happy with Forgejo and would still recommend it if people ask for my opinion.

[1]: https://codeberg.org/forgejo/forgejo/issues/5049

[kurante]

This is a bad faith comment in so many layers:

- The provided reason given was due to user accessibility concerns complicated by what likely is a breaking change.

- Even if you don't agree with the claim, a reserved name isn't unreasonable at all. Not to make a standard of GitHub, but the `admin` username is reserved there too.

- Dismissing an entire product based on a single non-critical technical limitation while simultaneously not contributing to the solution (unless you have a different username there, happy to be corrected) is fundamentally toxic.

- All the while conflating two separate products (Anubis and Forgejo) that aren't related at all.

- And that Anubis offers a non-anime girl solution, and is MIT Licensed if you really don't care for supporting the author.

I'm not going to prod at the "and everything else" part either.