19 ms·

Gitlab 13.1

190 points by bjoko 6y ago

thereyougo 6y ago
"This month's Most Valuable Person (MVP) is Jacopo Beschi " What a cool company culture. telling people they are doing good in person is nice, telling it to them and also sharing it with the world is great
- leipert 6y ago
  GitLab employee here: The MVPs are not employees, but community contributors as outlined here: https://about.gitlab.com/community/mvp/ https://about.gitlab.com/community/mvp/ But yes, I agree: it is very nice to share the achievements of our OSS contributors with the world :)
  - harrisonjackson 6y ago
    TIL! That is awesome and as a customer/user I'd love to see internal recognition, too! Maybe this would detract from the actual efforts of the other employees but it doesn't necessarily have to be employee of the month - could just be Kudos to X and Y for knocking out this lingering bug or adding this most wanted feature.
    - sytse 6y ago
      I agree recognition is important. We have an internal #thanks channel that got 20+ posts today of people being thanked. Also more than 10% of the company gets a $1000 discretionary bonus every month. We're doing an experiment of making videos for some of these bonuses that optionally can be made public.
AaronFriel 6y ago
If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,943 requests were made for 319 MB of resources over 30.06 seconds A staggering rate of 100 requests per second that persists indefinitely - I have no reason to believe the refresh loop is broken at any point.
- boleary-gl 6y ago
  GitLab technical evangelist here. I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?
  - deleted 6y ago
    [deleted]
  - AaronFriel 6y ago
    Yes, the page infinitely navigates back to itself resulting in a whole page refresh.
  - Earwig 6y ago
    Same issue here as the original post and similar extensions. I followed the suggestion of clearing cookies for about.gitlab.com and it doesn't help.
    - boleary-gl 6y ago
      We're working on this issue here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8052 https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8052. Hardest part - like much of software engineering - is trying to figure out how to reproduce it.
- jeandp 6y ago
  @AaronFriel try deleting your cookies for the website and see if that resolves it. I recall someone at GitLab having that problem the other day and think I recall that clearing their cookies fixed the issue for them. Either way I'll notify our marketing website team to have a look at this.
  - AaronFriel 6y ago
    One thing to look at is that the page does at least one whole page refresh by default, even an incognito window. If I open up the page in incognito, I see two requests in the network tab for https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/ https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-rel...
dindresto 6y ago
With 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.
- dindresto 6y ago
  I'm not saying they should remove any free features, but now and then it'd be nice seeing a Silver feature come to Bronze.
- bryanlarsen 6y ago
  Merge Request Reviews was moved to core as part of this release.
  - dindresto 6y ago
    Yes, this update basically reduced the value of Bronze significantly as there were no relevant new features coming to Bronze and those that we were paying for are now in the free tier.
- rakoo 6y ago
  Maybe the value is in ensuring the Gitlab team can continue working on the product, because they are paid to do so ?
- matthewcford 6y ago
  Same boat, although with GitHub pricing changes it’s more advantageous to switch. The fact that the security and dependency management is locked at gold when they are free on Github is annoying.
  - matthewcford 6y ago
    Moving breakman into core is nice but not enough
- kennyGitLab 6y ago
  Just a quick search of GitLab issues for "to Starter" and I came across the following: - https://gitlab.com/gitlab-org/gitlab/-/issues/10107 https://gitlab.com/gitlab-org/gitlab/-/issues/10107 In general our "Why Starter" page has some great rationale for why we encourage small teams to utilize GitLab Starter/Bronze. https://about.gitlab.com/pricing/starter/ https://about.gitlab.com/pricing/starter/
threeseed 6y ago
It'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 seriously needs to step back and think about how to simplify the interface. Because it's starting to get a bit ridiculous.
- sytse 6y ago
  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 example.
  - threeseed 6y ago
    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.
    - sytse 6y ago
      Thanks for the examples. BYW There is also a reply in this thread from a GitLab UX team-member who responds to a comment about the thumbs up/down and report abuse buttons https://news.ycombinator.com/item?id=23606854 https://news.ycombinator.com/item?id=23606854
- lttlrck 6y ago
  Yes agree completely. I'd love to whittle down the noise.
- rossmohax 6y ago
  > 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 kubernetes integration, monitoring, feature flags, Geo, backup procedure. Who in the right mind is going to enable Web Application Firewall feature, when rules exceptions cannot be configured? Somewhere in comments here will be reply from Gitlab employee, saying that dogfooding is something they are constantly working on, it doesn't matter. 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, so that poor devops engineers don't have to rediscover all the pain and come prepared. Just to be clear, Gitlab is an awesome tool, it is just not as awesome as their marketing wants us to believe.
candiddevmike 6y ago
The 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?
- threeseed 6y ago
  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 Issue button. But it's given the same size and prominence. Is abuse really as common as creating new issues ? 3) Backgrounds. Some are light grey. Some are dark grey. Some buttons background is filled, others solid.
  - jeldergl 6y ago
    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/ https://emojipedia.org/thumbs-up/). It’d be possible to use our custom icon library (http://gitlab-org.gitlab.io/gitlab-svgs/?q=thumb- 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 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 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 https://gitlab.com/gitlab-org/gitlab-ui/-/issues/627 and https://gitlab.com/groups/gitlab-org/-/epics/2964 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 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-button--default 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=%E2%9C%93&state=opened&search=deprecate+buttons 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!
citrus1330 6y ago
I love GitLab Better UI than GitHub and was first to provide free private repos
- kingbirdy 6y ago
  Bitbucket provided free private repos before Gitlab existed
  - kroltan 6y ago
    Severely limited* free private repos
  - 0xy 6y ago
    If only Bitbucket wasn't a typical Atlassian disaster it might be more popular. I've never used an Atlassian product that wasn't one of the slowest websites I've ever seen with an over-complicated UX that can only be described as sadistic (have you seen the multiple settings pages?). Gitlab and GitHub both blow Bitbucket out of the water, it's not even a competition.
- efiecho 6y ago
  > Better UI than GitHub I think that GitHub has a much better UI than GitLab. GitLab is slow and bloated compared to GitHub. Requiring Javascript for browsing the code repository is just bad design.
  - deleted 6y ago
    [deleted]
  - samdbeckham 6y ago
    GitLab employee here. As much as it pains me, I have to agree with you for the most part. Performance is one of the biggest pain points for our frontend team, but is something we're actively working on. Here's one of our epics to show our progress: https://gitlab.com/groups/gitlab-org/-/epics/716 https://gitlab.com/groups/gitlab-org/-/epics/716 We're in the process of migrating parts of our codebase from haml templates to Vue apps, which does have the unfortunate downside of requiring javascript to run. We're looking into solving this with server side rendering, but it's early days right now. Here's the issue for that: https://gitlab.com/gitlab-org/gitlab/-/issues/215365 https://gitlab.com/gitlab-org/gitlab/-/issues/215365 If either of these things are things you could help with, we encourage you to contribute and help us make GitLab a better place.
rpadovani 6y ago
It is not in the blog post probably because it is still in Alpha, but Gitlab now has a Dark Theme <3 Settings -> Preferences: there is a new theme called "Dark Mode (Alpha). Indeed still in Alpha, but I love they are working on this!
- leipert 6y ago
  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 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)
- robotmay 6y ago
  Welp, this is confirmation that I haven't been keeping up on everything going on; when I learn about my most desired feature on my company's software from a Hacker News post :S
- ashton314 6y ago
  Yay! Tbh I like what it looks like with Dark Reader better: the background is still to bright to my eyes. Any word on when the dark mode will be ready for HN? I saw there was a thread a month or two ago about this.
deleted 6y ago
[deleted]
dan1234 6y ago
Looks like WebAuthn is still missing, even though there seem to have been merge requests featuring it forever! Anyone know which milestone it’ll be merged into?
- sytse 6y ago
  This relevant MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692 is scheduled (not guarateed) for 13.2 (July 22, 2020). Also see this issue https://gitlab.com/gitlab-org/gitlab/-/issues/22506 https://gitlab.com/gitlab-org/gitlab/-/issues/22506
  - dan1234 6y ago
    Thanks for the update, I’ve looking forward to this feature for around 6 months!
jtwaleson 6y ago
I somehow had a feeling Gitlab would be bought this year, but the list dramatically falls apart upon closer inspection: - Google: will never work, completely different mindset and engineering culture. Gitlab feels way too unrefined (in a good sense). - AWS: Gitlab is already too different from their tech, and will never be that tightly coupled with the rest of AWS. - IBM: :') they wish - MS: already has GitHub Any others? I think any giant company would have a hard time integrating all-remote Gitlab.
- travbrack 6y ago
  I think you're underestimating the power of a boatload of cash. All of the companies you listed could afford to buy gitlab.
  - jtwaleson 6y ago
    Sure they could, but it still needs to make sense from either a growth or a defense play. I don't see that for any of these companies.
- stock_toaster 6y ago
  > I think any giant company would have a hard time integrating all-remote Gitlab. Atlassian maybe? (shudder)
  - jbay808 6y ago
    Don't they already have Bitbucket?
    - johnbellone 6y ago
      They do, along with several other competing products.
    - fomine3 6y ago
      They bought Trello even they have Jira
apple4ever 6y ago
LOVE that Merge Request Reviews have moved to core!!
yters 6y ago
What makes Gitlab significantly better than the other gitlings?
- znpy 6y ago
  the gitlab-ci is the killer app. also, the fact that you can self-host it and it's very easy to do so.
  - yters 6y ago
    how is that better than jenkins?
- mdaniel 6y ago
  IMHO, it's integration. znpy was correct, but incomplete: GitLab ships with CI/CD, secrets management via Vault, AWS ECS integration, Kubernetes integration, issue tracking, wiki, an artifact repository for 5 major package types, metrics, alerts, and even a full-blown Slack competitor (optional, of course) You can absolutely integrate your favorite, and/or best of breed, tools with any git hosting software that you'd like -- but that takes non-zero time to do and upgrading them will also be non-zero time. GitLab ships like a machine every month, and it seems this feature announcement is representative of the caliber of every release
  - yters 6y ago
    does it make sense to switch to gitlab if one already has most of those things integrated?
elmolino89 6y ago
Version control for GitLab wiki is still not there. Supposedly it will be in 13.2. For a small shop using GitLab local install versioning of the systems/software/lab protocols documentation is something hard to live without.
- cdybenko 6y ago
  Hey GitLab Wiki PM here! We do have an issue scheduled in 13.2 for Wiki diffing. However this still won't allow you to revert a change but will visually help you see the diffs line by line (just like in MRs): https://gitlab.com/gitlab-org/gitlab/-/issues/15242 https://gitlab.com/gitlab-org/gitlab/-/issues/15242 (FYI that issue is a community contribution so I can't guarantee it will ship in 13.2, but we'll try!) I'm sure you're aware, we also have git versions of the wiki in the UI: https://docs.gitlab.com/ee/user/project/wiki/#viewing-the-history-of-a-wiki-page https://docs.gitlab.com/ee/user/project/wiki/#viewing-the-hi... Can you tell me more about your use case for versioning?
  - elmolino89 6y ago
    Sorry for the late reply. Few features (apart from be able to view wiki diffs) from my point of view: 1. Wiki edits in activity 2. User wiki edit history (= edits times, pages, size of diffs) Maybe in a long run it will be good to have Markdown based collaborative document editing. Meaning that each editor can branch the draft doc, introduce changes. Then these branches will need to be reviewed and merged, probably by 1-2 people. Hope it helps

190 points by bjoko 6y ago

"This month's Most Valuable Person (MVP) is Jacopo Beschi " What a cool company culture. telling people they are doing good in person is nice, telling it to them and also sharing it with the world is great

leipert 6y ago
GitLab employee here: The MVPs are not employees, but community contributors as outlined here: https://about.gitlab.com/community/mvp/ https://about.gitlab.com/community/mvp/ But yes, I agree: it is very nice to share the achievements of our OSS contributors with the world :)
- harrisonjackson 6y ago
  TIL! That is awesome and as a customer/user I'd love to see internal recognition, too! Maybe this would detract from the actual efforts of the other employees but it doesn't necessarily have to be employee of the month - could just be Kudos to X and Y for knocking out this lingering bug or adding this most wanted feature.
  - sytse 6y ago
    I agree recognition is important. We have an internal #thanks channel that got 20+ posts today of people being thanked. Also more than 10% of the company gets a $1000 discretionary bonus every month. We're doing an experiment of making videos for some of these bonuses that optionally can be made public.

AaronFriel 6y ago

If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,943 requests were made for 319 MB of resources over 30.06 seconds A staggering rate of 100 requests per second that persists indefinitely - I have no reason to believe the refresh loop is broken at any point.

boleary-gl 6y ago
GitLab technical evangelist here. I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?
- deleted 6y ago
  [deleted]
- AaronFriel 6y ago
  Yes, the page infinitely navigates back to itself resulting in a whole page refresh.
- Earwig 6y ago
  Same issue here as the original post and similar extensions. I followed the suggestion of clearing cookies for about.gitlab.com and it doesn't help.
  - boleary-gl 6y ago
    We're working on this issue here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8052 https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8052. Hardest part - like much of software engineering - is trying to figure out how to reproduce it.
jeandp 6y ago
@AaronFriel try deleting your cookies for the website and see if that resolves it. I recall someone at GitLab having that problem the other day and think I recall that clearing their cookies fixed the issue for them. Either way I'll notify our marketing website team to have a look at this.
- AaronFriel 6y ago
  One thing to look at is that the page does at least one whole page refresh by default, even an incognito window. If I open up the page in incognito, I see two requests in the network tab for https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/ https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-rel...

dindresto 6y ago

With 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.

dindresto 6y ago
I'm not saying they should remove any free features, but now and then it'd be nice seeing a Silver feature come to Bronze.
bryanlarsen 6y ago
Merge Request Reviews was moved to core as part of this release.
- dindresto 6y ago
  Yes, this update basically reduced the value of Bronze significantly as there were no relevant new features coming to Bronze and those that we were paying for are now in the free tier.
rakoo 6y ago
Maybe the value is in ensuring the Gitlab team can continue working on the product, because they are paid to do so ?
matthewcford 6y ago
Same boat, although with GitHub pricing changes it’s more advantageous to switch. The fact that the security and dependency management is locked at gold when they are free on Github is annoying.
- matthewcford 6y ago
  Moving breakman into core is nice but not enough
kennyGitLab 6y ago
Just a quick search of GitLab issues for "to Starter" and I came across the following: - https://gitlab.com/gitlab-org/gitlab/-/issues/10107 https://gitlab.com/gitlab-org/gitlab/-/issues/10107 In general our "Why Starter" page has some great rationale for why we encourage small teams to utilize GitLab Starter/Bronze. https://about.gitlab.com/pricing/starter/ https://about.gitlab.com/pricing/starter/

threeseed 6y ago

It'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 seriously needs to step back and think about how to simplify the interface. Because it's starting to get a bit ridiculous.

sytse 6y ago
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 example.
- threeseed 6y ago
  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.
  - sytse 6y ago
    Thanks for the examples. BYW There is also a reply in this thread from a GitLab UX team-member who responds to a comment about the thumbs up/down and report abuse buttons https://news.ycombinator.com/item?id=23606854 https://news.ycombinator.com/item?id=23606854
lttlrck 6y ago
Yes agree completely. I'd love to whittle down the noise.
rossmohax 6y ago
> 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 kubernetes integration, monitoring, feature flags, Geo, backup procedure. Who in the right mind is going to enable Web Application Firewall feature, when rules exceptions cannot be configured? Somewhere in comments here will be reply from Gitlab employee, saying that dogfooding is something they are constantly working on, it doesn't matter. 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, so that poor devops engineers don't have to rediscover all the pain and come prepared. Just to be clear, Gitlab is an awesome tool, it is just not as awesome as their marketing wants us to believe.

candiddevmike 6y ago

The 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?

threeseed 6y ago
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 Issue button. But it's given the same size and prominence. Is abuse really as common as creating new issues ? 3) Backgrounds. Some are light grey. Some are dark grey. Some buttons background is filled, others solid.
- jeldergl 6y ago
  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/ https://emojipedia.org/thumbs-up/). It’d be possible to use our custom icon library (http://gitlab-org.gitlab.io/gitlab-svgs/?q=thumb- 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 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 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 https://gitlab.com/gitlab-org/gitlab-ui/-/issues/627 and https://gitlab.com/groups/gitlab-org/-/epics/2964 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 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-button--default 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=%E2%9C%93&state=opened&search=deprecate+buttons 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!

citrus1330 6y ago

I love GitLab Better UI than GitHub and was first to provide free private repos

kingbirdy 6y ago
Bitbucket provided free private repos before Gitlab existed
- kroltan 6y ago
  Severely limited* free private repos
- 0xy 6y ago
  If only Bitbucket wasn't a typical Atlassian disaster it might be more popular. I've never used an Atlassian product that wasn't one of the slowest websites I've ever seen with an over-complicated UX that can only be described as sadistic (have you seen the multiple settings pages?). Gitlab and GitHub both blow Bitbucket out of the water, it's not even a competition.
efiecho 6y ago
> Better UI than GitHub I think that GitHub has a much better UI than GitLab. GitLab is slow and bloated compared to GitHub. Requiring Javascript for browsing the code repository is just bad design.
- deleted 6y ago
  [deleted]
- samdbeckham 6y ago
  GitLab employee here. As much as it pains me, I have to agree with you for the most part. Performance is one of the biggest pain points for our frontend team, but is something we're actively working on. Here's one of our epics to show our progress: https://gitlab.com/groups/gitlab-org/-/epics/716 https://gitlab.com/groups/gitlab-org/-/epics/716 We're in the process of migrating parts of our codebase from haml templates to Vue apps, which does have the unfortunate downside of requiring javascript to run. We're looking into solving this with server side rendering, but it's early days right now. Here's the issue for that: https://gitlab.com/gitlab-org/gitlab/-/issues/215365 https://gitlab.com/gitlab-org/gitlab/-/issues/215365 If either of these things are things you could help with, we encourage you to contribute and help us make GitLab a better place.

rpadovani 6y ago

It is not in the blog post probably because it is still in Alpha, but Gitlab now has a Dark Theme <3 Settings -> Preferences: there is a new theme called "Dark Mode (Alpha). Indeed still in Alpha, but I love they are working on this!

leipert 6y ago
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 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)
robotmay 6y ago
Welp, this is confirmation that I haven't been keeping up on everything going on; when I learn about my most desired feature on my company's software from a Hacker News post :S
ashton314 6y ago
Yay! Tbh I like what it looks like with Dark Reader better: the background is still to bright to my eyes. Any word on when the dark mode will be ready for HN? I saw there was a thread a month or two ago about this.

deleted 6y ago

[deleted]

dan1234 6y ago

Looks like WebAuthn is still missing, even though there seem to have been merge requests featuring it forever! Anyone know which milestone it’ll be merged into?

sytse 6y ago
This relevant MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692 is scheduled (not guarateed) for 13.2 (July 22, 2020). Also see this issue https://gitlab.com/gitlab-org/gitlab/-/issues/22506 https://gitlab.com/gitlab-org/gitlab/-/issues/22506
- dan1234 6y ago
  Thanks for the update, I’ve looking forward to this feature for around 6 months!

jtwaleson 6y ago

I somehow had a feeling Gitlab would be bought this year, but the list dramatically falls apart upon closer inspection: - Google: will never work, completely different mindset and engineering culture. Gitlab feels way too unrefined (in a good sense). - AWS: Gitlab is already too different from their tech, and will never be that tightly coupled with the rest of AWS. - IBM: :') they wish - MS: already has GitHub Any others? I think any giant company would have a hard time integrating all-remote Gitlab.

travbrack 6y ago
I think you're underestimating the power of a boatload of cash. All of the companies you listed could afford to buy gitlab.
- jtwaleson 6y ago
  Sure they could, but it still needs to make sense from either a growth or a defense play. I don't see that for any of these companies.
stock_toaster 6y ago
> I think any giant company would have a hard time integrating all-remote Gitlab. Atlassian maybe? (shudder)
- jbay808 6y ago
  Don't they already have Bitbucket?
  - johnbellone 6y ago
    They do, along with several other competing products.
  - fomine3 6y ago
    They bought Trello even they have Jira

apple4ever 6y ago

LOVE that Merge Request Reviews have moved to core!!

yters 6y ago

What makes Gitlab significantly better than the other gitlings?

znpy 6y ago
the gitlab-ci is the killer app. also, the fact that you can self-host it and it's very easy to do so.
- yters 6y ago
  how is that better than jenkins?
mdaniel 6y ago
IMHO, it's integration. znpy was correct, but incomplete: GitLab ships with CI/CD, secrets management via Vault, AWS ECS integration, Kubernetes integration, issue tracking, wiki, an artifact repository for 5 major package types, metrics, alerts, and even a full-blown Slack competitor (optional, of course) You can absolutely integrate your favorite, and/or best of breed, tools with any git hosting software that you'd like -- but that takes non-zero time to do and upgrading them will also be non-zero time. GitLab ships like a machine every month, and it seems this feature announcement is representative of the caliber of every release
- yters 6y ago
  does it make sense to switch to gitlab if one already has most of those things integrated?

elmolino89 6y ago

Version control for GitLab wiki is still not there. Supposedly it will be in 13.2. For a small shop using GitLab local install versioning of the systems/software/lab protocols documentation is something hard to live without.

cdybenko 6y ago
Hey GitLab Wiki PM here! We do have an issue scheduled in 13.2 for Wiki diffing. However this still won't allow you to revert a change but will visually help you see the diffs line by line (just like in MRs): https://gitlab.com/gitlab-org/gitlab/-/issues/15242 https://gitlab.com/gitlab-org/gitlab/-/issues/15242 (FYI that issue is a community contribution so I can't guarantee it will ship in 13.2, but we'll try!) I'm sure you're aware, we also have git versions of the wiki in the UI: https://docs.gitlab.com/ee/user/project/wiki/#viewing-the-history-of-a-wiki-page https://docs.gitlab.com/ee/user/project/wiki/#viewing-the-hi... Can you tell me more about your use case for versioning?
- elmolino89 6y ago
  Sorry for the late reply. Few features (apart from be able to view wiki diffs) from my point of view: 1. Wiki edits in activity 2. User wiki edit history (= edits times, pages, size of diffs) Maybe in a long run it will be good to have Markdown based collaborative document editing. Meaning that each editor can branch the draft doc, introduce changes. Then these branches will need to be reviewed and merged, probably by 1-2 people. Hope it helps