Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

about.gitlab.com

Post reply on HN
Print view View original

11–20 of 49 posts

Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

#11

Post by sslalready »

Speaking 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 ability to create a pipeline that's not connected to a specific Git branch. I'd like to be able to create a pipeline that can be triggered manually, without first having to create a dummy branch to put a .gitlab-ci.yml there. Is that something that's on your roadmap?

Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

#12

Post by YorickPeterse »

antarrah wrote: post #6

Please fix the speed. Even your gifs are slow.

Plenty of work is being done in terms of performance improvements, and almost every release features a large set of improvements. A list of all performance related merge requests that have been merged can be found at https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope....

If you'd like to help out you can read up on the contributing guidelines at https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBU....

Alternatively, any issues with data on what is slow and how these patterns can be reproduced is also greatly appreciated!

Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

#13

Post by jobvandervoort »

antarrah wrote: post #6

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

Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

#16

Post by liquidise »

kevinsd wrote: post #14

And squash merge is still an ee-only (paid-only) feature ¯\_(ツ)_/¯

I do not understand the appeal of squashed merges. The only pro i know of is the ease of reverting a merge. On the cons side: you obfuscate an entire branch into a single commit, effectively making git-bisect useless. Furthermore, if multiple people collaborate on a branch, all code blames to one person, quite literally rewriting the code history.

Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

#17

Post by foepys »

sslalready wrote: post #11

Speaking 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…

I find the whole design of GitLab not appealing to my eye. The recent redesign was a step in the right direction but I am still missing visible separators (e.g. boxes, lines, colored background) between/around areas for example on the page of an issue.

Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor

#20

Post by andreasmarc »

sslalready wrote: post #11

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

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/13680

[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/22192

Post reply on HN