I love GitLab
Better UI than GitHub and was first to provide free private repos
Gitlab 13.1
21–30 of 90 posts
Re: Gitlab 13.1
#22It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…
This comment makes a lot of good points. I think we can stop recommending License and Contributors since GitLab is mostly used for closed source software. The templates will still be there but just not suggested until you started to create a new file. And you should be able to disable everything but the repo if you want to. And of course you can disable the repo as well if you just want the planning features for exam…
Also please put in place this simple UI rule: "If it doesn't need attention don't make it coloured or bold"
e.g. thumbs up/down, report abuse etc.
Re: Gitlab 13.1
#23It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…
> It's great and impressive how quick Gitlab moves in adding new features. Don't trust their feature list, they often "forget" to use it themselves. Many of those features are there to tick the box and daze executives, but are barely usable in practice. It took them a year to start supporting Kubernetes clusters with RBAC, they didn't use autodevops for their own releases, even for simple components, nor any kubernet…
"Somewhere in comments here will be reply from Gitlab employee, saying that dogfooding is something they are constantly working on"
To ensure we meet your expectations I want to state that we're continuously working on dogfooding, you can track our progress in https://gitlab.com/gitlab-org/gitlab/-/issues?label_name=Dog...
"What they should be doing is to update documentation pages with feature maturity level and have a block of links to most popular bugs related to the feature"
That is a great idea and I wonder if https://about.gitlab.com/direction/maturity/ meets your expectations. We recently update the criteria for viable and complete to incorporate dogfooding:
- Viable: Significant use at GitLab the company.
- Complete: GitLab the company dogfoods it exclusively.
And thanks for calling us an awesome tool. Hope you don't mind the tongue-in-cheek response at the top of my comment :)
Re: Gitlab 13.1
#24It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…
>Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them.
You can do it in Settings > General > "Visibility, project features, permissions"
Re: Gitlab 13.1
#25It is not in the blog post probably because it is still in Alpha, but Gitlab now has a Dark Theme Settings -> Preferences: there is a new theme called "Dark Mode (Alpha). Indeed still in Alpha, but I love they are working on this!
Re: Gitlab 13.1
#26[deleted]
Re: Gitlab 13.1
#27I love GitLab Better UI than GitHub and was first to provide free private repos
Bitbucket provided free private repos before Gitlab existed
Re: Gitlab 13.1
#28It is not in the blog post probably because it is still in Alpha, but Gitlab now has a Dark Theme Settings -> Preferences: there is a new theme called "Dark Mode (Alpha). Indeed still in Alpha, but I love they are working on this!
Before you file an issue, double check if an issue for the problems you experience with the Dark Mode already exists in this epic: https://gitlab.com/groups/gitlab-org/-/epics/2902
And of course: have fun on the dark side (as they are the ones with the cookies)
Re: Gitlab 13.1
#29With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.
Maybe the value is in ensuring the Gitlab team can continue working on the product, because they are paid to do so ?
Re: Gitlab 13.1
#30The alert integration looks interesting, but the screenshots for code intelligence look awful. Who decided to use a super light shade of gray on a white background?
Their UI has a lot of these annoying issues and they never seemed to get around to fixing them. My other favourites: 1) UI is all muted and grey which is great because it allows you to focus on your code, issues etc. Well except for the Thumbs Up/Down buttons which are a bright yellow and the only thing to stand out. And it's a feature that serves no purpose in most cases. 2) Report Abuse button is next to the New Is…
Thanks for adding your thoughts, hopefully I can shed some light in a few places.
1) I’m assuming you’re referring to the emoji buttons. They are useful to determine upvotes and downvotes on issues and merge requests. These counts can be used when sorting for popularity. We leverage system emoji here and in most cases they are a bright yellow (https://emojipedia.org/thumbs-up/). It’d be possible to use our custom icon library (http://gitlab-org.gitlab.io/gitlab-svgs/?q=thumb-) for these buttons, but then they wouldn’t visually align with other award emoji that can be added inline. Here’s more info https://docs.gitlab.com/ee/user/award_emojis.html.
2) If you don’t have permission to close the issue (or merge request), you will only see the 'Report abuse' button (I’m guessing this is what you’re seeing), otherwise there would be a split button with 'Close issue' as the default option, and 'Report abuse' as the second. I agree that this needs some further consideration, so I opened an issue to start a discussion https://gitlab.com/gitlab-org/gitlab/-/issues/223775. Feel free to contribute and add your thoughts there too.
3) A few things are at work here. We recently updated our neutral palette to normalize it with the rest of the color palette, and address some accessibility items. We’re working on updating the neutral variables and remap them throughout the product, see https://gitlab.com/gitlab-org/gitlab-ui/-/issues/627 and https://gitlab.com/groups/gitlab-org/-/epics/2964. If there’s anything you don’t think would be addressed by those changes, it’d be great if you could open a new issue (https://gitlab.com/gitlab-org/gitlab/-/issues/new) and cc the UX designers (@gitlab-com/gitlab-ux/designers). Regarding buttons, we are in the process of replacing deprecated buttons in the product with new ones from GitLab UI https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/base-but.... Here are a few issues covering that effort https://gitlab.com/gitlab-org/gitlab/-/issues?scope=all&utf8.... Many other issues will be created to do the same in other parts of the product.
I hope this helps, thanks again for your comments!