6 ms·
Personally, I also think, GitHub's Checks API, and it Github bots. Gives a much better experience compared to GitLab. On a daily basis I am confused about how
by wdb 6y ago
Personally, I also think, GitHub's Checks API, and it Github bots. Gives a much better experience compared to GitLab.
On a daily basis I am confused about how diff's are being rendered in GitLab merge requests, as it has a weird way to render ${blah} in strings in lines.
Also when you want to check if an issue exists in GitLab own repository, you always end up in some jungle of redirected tickets. Just now I got redirected to three different tickets , as they switch projects or something. Really annoying.
- boleary-gl 6y agoCan you share an example or screenshot of what you mean around the rendering issue in merge requests? As for the issue redirects - it does stink. It's an artifact of our move to a single code base for CE and EE [1]. A lot of issues have long-standing SEO so the "old" issue often comes up in a Google search. [1] https://about.gitlab.com/blog/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/ https://about.gitlab.com/blog/2019/08/23/a-single-codebase-f...
- wdb 6y agoYes, for example, in today's pull request, I added a new file and now in my Typescript file it renders things like this, which I find confusing: https://imgur.com/a/C82hcMK https://imgur.com/a/C82hcMK