That was not what I titled it though.
I can't explain how it changed to "Gitlab is now in the fortune 500".
It was originally "Why this 'well-kept' secret for programmers is suddenly popping up in the Fortune 500", I shortened it by removing the "popping it".
Sorry for the inconvenience.
We're relatively new to the GitLab game, but it has vastly improved the overall transparency into our codebase and the work that's going into it. The ability to put comments in the diffs as code reviews is something that a lot of people might be used to, but we've been sorely missing as my company.
I've read other people's gripes, but I have none of my own yet. Thanks very much GitLab team.
There are 26 million employees in the Fortune 500. If you manage to make a technology product that isn't being used by one of them, please let me know.
Can we expect to see more focus on improving merge requests within Gitlab? I've felt as though for the longest time it's not had any of the major functionality gaps filled and seems to be deteriorating with each release. I'm wondering now if Gitlab doesn't see it very high on the list of priorities for the product
(Apologies if this comes across as overly negative, I use Gitlab all day every day and it's a great tool)
Absolutely. Code review is at the core of the product and it should be amazing to use.
Coming up we will add the ability to revert merges [0]. We're also working on redoing the UI of MRs (and much of the rest of the app) and have someone working fulltime on performance now, which will also help here.
What would you like to see improved? Very curious to hear.
That's great to hear! Specifically, the lack of syntax highlighting on merge reviews is a killer feature. My team actually temporarily moved over to Phabricator, specifically for this feature.
- Currently the only way for someone to indicate that a merge request is good to merge is by contacting them outside of Gitlab or doing the upvote on the MR, which fascinatingly is only possible by commenting with a :+1: thumbs up
- Also multiple assignees on MRs
- Ability for anyone to add labels to an MR, not just the assignee
- On the index page listing MR's I've often felt like a solid improvement would be to show both author and assignee. I think Gitlab has alternated between one or the other a few times on this page but both seem to me to be pertinent information.
We solved this with the 'approvers' feature. We still want to only have a single assignee, as only a single person can click 'merge'.
> Ability for anyone to add labels to an MR, not just the assignee
This should be anyone with editing rights to the MR, such as masters. We're improving the UX to make this easier in GitLab 8.2 or 8.3 (also creating labels on the fly and quickly adding more).
> On the index page listing MR's I've often felt like a solid improvement would be to show both author and assignee. I think Gitlab has alternated between one or the other a few times on this page but both seem to me to be pertinent information.
Article title is: "Why this 'well-kept' secret for programmers is suddenly popping up in the Fortune 500" which we are happy with. Maybe HN title can be changed.