Git’s submodule support is hella buggy, so if you use submodules with the FETCH Git strategy then it will break. Gitlab needs a fallback where it deletes the repo and clones from scratch. Unfortunately they won’t do that because they don’t want to have to redownload blobs (and somehow they think completely breaking is better?)
You can collapse log output in CI, but you have to decide in advance whether a section is collapsed - you can’t put the collapse marker in the closing tag. Quite annoying.
The built-in CI sections (cloning, cleaning up at the end etc.) are extremely verbose (especially with submodules) and can’t be collapsed by default, making the log output very annoying - you always have to scroll up to see the actual end of the log.
There’s a bug where sometimes pipelines don’t run at all, if you configure your workflow rules to not run merge request pipelines.
There’s a bug where sometimes git authentication fails for the first time a new submodule is added to a project.
The quick search thingy sometimes fails to find a project even if you type it in exactly. I haven’t looked into that.
You can’t configure the max length of merge trains. It’s hard-coded to 20.
There’s loads more… this is just what I remember off the top of my head.
Pretty much any time you find a bug you’ll discover a 5 year old issue with some “A large premium customer is requesting this” comments.
I mostly like Gitlab but it has quite a lot of bugs once you use it in anger. It’s doubly annoying because I can’t really debug them even with the source code, because it’s written in untyped Ruby and that is basically the worst case scenario if you want to follow a large code base. Even Phabricator (PHP) was easier to work on.
I haven’t looked into the Forgejo code but it’s written in Go so it is guaranteed to be a lot easier to work on, and probably less buggy.
There are so many basic issues with Gitlab I wish they would fix rather than adding AI.
And I definitely think there is space for AI, particularly in code review and triaging issues. But it doesn’t look like Duo does either of those?
What are those issues? I use gitlab for personal use and for a small group of people at work so I’m curious.
Various things I’ve run into:
Git’s submodule support is hella buggy, so if you use submodules with the
FETCHGit strategy then it will break. Gitlab needs a fallback where it deletes the repo and clones from scratch. Unfortunately they won’t do that because they don’t want to have to redownload blobs (and somehow they think completely breaking is better?)You can collapse log output in CI, but you have to decide in advance whether a section is collapsed - you can’t put the collapse marker in the closing tag. Quite annoying.
The built-in CI sections (cloning, cleaning up at the end etc.) are extremely verbose (especially with submodules) and can’t be collapsed by default, making the log output very annoying - you always have to scroll up to see the actual end of the log.
There’s a bug where sometimes pipelines don’t run at all, if you configure your workflow rules to not run merge request pipelines.
There’s a bug where sometimes git authentication fails for the first time a new submodule is added to a project.
The quick search thingy sometimes fails to find a project even if you type it in exactly. I haven’t looked into that.
You can’t configure the max length of merge trains. It’s hard-coded to 20.
There’s loads more… this is just what I remember off the top of my head.
Pretty much any time you find a bug you’ll discover a 5 year old issue with some “A large premium customer is requesting this” comments.
I mostly like Gitlab but it has quite a lot of bugs once you use it in anger. It’s doubly annoying because I can’t really debug them even with the source code, because it’s written in untyped Ruby and that is basically the worst case scenario if you want to follow a large code base. Even Phabricator (PHP) was easier to work on.
I haven’t looked into the Forgejo code but it’s written in Go so it is guaranteed to be a lot easier to work on, and probably less buggy.