Please fix the speed. Even your gifs are slow.
We're working hard on making GitLab.com faster (where I also made the gifs) [0]. If you're running your own instance, it should be fast. [0]: https://gitlab.com/gitlab-com/infrastructure/issues/59
GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
31–40 of 49 posts
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#32Please fix the speed. Even your gifs are slow.
We're working hard on making GitLab.com faster (where I also made the gifs) [0]. If you're running your own instance, it should be fast. [0]: https://gitlab.com/gitlab-com/infrastructure/issues/59
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#33Speaking of UX, would you consider improving the look of Markdown rendered text (usually README.md ) in the repo browser? On GitHub they look great and it's a pleasure reading Markdown formatted text there. In GitLab it's however not very appealing. Headers, spacing between them and paragraphs doesn't look very good IMO. Coming from a previous job where we used GitHub and TeamCity, something I miss with GitLab is the…
Regarding Markdown renderering, from my perspective the most important improvement is reducing the line width to a better readable character length. This is already addressed [0] and on the list for the 8.14 release. I agree that the spacing can be improved. In general, my impression is that there is a good awareness for required UI improvements [1] in the GitLab team. So I’m looking forward to the upcoming releases.…
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#34Another release we're very proud of. Much of the work this release we spent on improving our idea to production flow and demos [0], things that'll trickly in over the coming releases. We're also focusing on some longer-term improvements in UX [1], and are happy to ship some nice iterations with issue boards and merge conflict resolution. Lastly, we're slowly building up review apps, which allow you to see/play with/t…
review apps are super exciting! That's the exact kind of interface I've been hoping for. I really hope it's available like the commit status api is (we use that for posting our custom CI builds). We currently have our own review app system at our company (and no hopes of switching to gitlab ci in the future - unfortunately :( ), but it'd be amazing if we could tie into it the same way we do for CI -- just "here's the…
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#35I am continuously blown away how quickly Gitlab is pushing out releases. It's been amazing to see the product grow over the years.
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#36Having a lot of issues with our merge requests never merging and just spinning forever.[1] Would like Gitlab to put a little more focus on those kinds of dealbreaker issues. Would hate to give up such a great product because of things like that. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/2995
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#37Since the GitLab folks hang around here... any chance you'll let us force a redirect to HTTPS for GitLab pages with custom domains? Loving GitLab so far though!
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#38Would it be possible to make the Board view default view when going into issues via some option?
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#39Earlier quoted context omitted.
I'm actually not sure if we do. Can you share me a link to an example? Seems like something very GitLab-esque to support.
Looks like the issue [0] had a milestone of 8.13 but it is still open. So, it didn't make the release? [0] https://gitlab.com/gitlab-org/gitlab-ce/issues/2508
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#40Having a lot of issues with our merge requests never merging and just spinning forever.[1] Would like Gitlab to put a little more focus on those kinds of dealbreaker issues. Would hate to give up such a great product because of things like that. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/2995
Thanks for posting, I mentioned one of our issue triage specialists in the issue.