Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by Merad on Tuesday September 17, 2019 @05:19PM
(#21000196)
Thanks for taking the time to respond!
Re squash commits: as a MR author what I want is the ability to set the commit message in advance (even if it's just a check box to say "use the MR title and description". Using a commit message is a sane default behavior, but not extremely helpful most of the time (IMO). If I'm going to rely on it for the message in my squashed commit I'm going to have to remember to check my branch history, and most of the time I'll probably have to do an interactive rebase to clean things up and ensure Gitlab grabs the correct commit message. It also negates the value of "squash on the server" - if I need to do an interactive rebase anyway, it only requires about 30 seconds extra to just do the squash myself.
Re:Gitlab More Than Doubles Valuation to $2.75B Ahead of Pla...
by emilycook on Tuesday September 17, 2019 @05:32PM
(#21000298)
Ahh gotcha, you seem to have pretty much the same feedback as this comment: https://gitlab.com/gitlab-org/gitlab-foss/issues/47149#note_.... Commenting on this issue (and tagging @ntepluhina, one of the owners of the issue) with your feedback would be the best way for someone to see it! I can pass on the info too, but issue comments take precedence when we're prioritizing.
> when you look at the team list in Gitlab, it shows everyone who has access to the team
This has been an ongoing issue for a while, but a fix is currently scheduled for 12.4: https://gitlab.com/gitlab-org/gitlab-foss/issues/44958
> server squashing commits
You don't have to provide a custom squash message, and the default behavior will be either (a) taken from the first multi-line commit message in the merge, or (b) the merge request’s title if no multi-line commit message is found.
Documentation: https://docs.gitlab.com/ee/user/project/merge_requests/squas...
The original issue around this: https://gitlab.com/gitlab-org/gitlab-foss/issues/47149