GitLab 8.17 Released with GitLab Pages in GitLab CE and Squash on Merge
1–6 of 6 posts
Re: GitLab 8.17 Released with GitLab Pages in GitLab CE and Squash on Merge
#2Nice! Excited about squash on merge finally making its way into Gitlab.
Re: GitLab 8.17 Released with GitLab Pages in GitLab CE and Squash on Merge
#3Consistently impressed and surprised with how quickly GitLab appear to be able to deliver value to users. I am certain that we will be using both Pages and Squash on Merge in the near future.
Re: GitLab 8.17 Released with GitLab Pages in GitLab CE and Squash on Merge
#4Nice! Excited about squash on merge finally making its way into Gitlab.
Great to hear; It has taken us a bit longer than we wanted, but we're happy it's here. Let us know if there are any further improvements we can make.
Re: GitLab 8.17 Released with GitLab Pages in GitLab CE and Squash on Merge
#5Nice! Excited about squash on merge finally making its way into Gitlab.
Great to hear; It has taken us a bit longer than we wanted, but we're happy it's here. Let us know if there are any further improvements we can make.
We've started using Gitlab at work and fully plan on getting off Github, just because the experience is so much better.
My only other issue is the the UI in the merge requests. It all seems to run together and it's difficult (for me at least) to get a handle on what's going on with comments and the status at the top.
Re: GitLab 8.17 Released with GitLab Pages in GitLab CE and Squash on Merge
#6Earlier quoted context omitted.
Great to hear; It has taken us a bit longer than we wanted, but we're happy it's here. Let us know if there are any further improvements we can make.
We've started using Gitlab at work and fully plan on getting off Github, just because the experience is so much better. My only other issue is the the UI in the merge requests. It all seems to run together and it's difficult (for me at least) to get a handle on what's going on with comments and the status at the top.
That's great to hear.
We're working on making it easier to see what is happening in merge requests. It's the intersection of much of GitLab's power [0]. I see some thing in the issue that might help your case, but I'm also sharing your comment there. If you have more comments, please feel free to leave them in that issue or to me directly.