Having 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.
GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
21–30 of 49 posts
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#22Another 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 link, it built succesfully!" would be a huge improvement to our workflow. Currently we treat it as a separate build (posting to status, with the url being the review app). Then because the URL didn't seem very visible on gitlab, we post it in the merge request too. Not nearly as nice as this would be!
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#23Does this release also support rendering Jupyter notebooks like github does?
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.
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#24And 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.
Its designed more for people who do master-based development and do a PR per commit. (But might add a couple commits fixing the PR)
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#25And squash merge is still an ee-only (paid-only) feature ¯\_(ツ)_/¯
What does this actually mean? Does their UI just fall apart if you force push after squashing in git rebase -i?
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#26Does this release also support rendering Jupyter notebooks like github does?
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?
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#27Speaking 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.
I have to agree. When I first started using Gitlab, it was quite jarring.
I'm much more happy with Gitlab's UI now that I've spent a lot of time with it. At least I don't fight with the interface after becoming familiar with it (it's no iTunes).
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#28Does this release also support rendering Jupyter notebooks like github does?
We are currently in the process of finding ways to implement many formats more quickly. It's certainly on our radars, although I can't promise it will make it into the next release.
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#29And 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.
Squash merge would be most useful in cases where someone turns in a PR and then there's back and forth which result in them making additional commit such like "Fix typo" and "Change struct name". That's not useful history and it's sometimes easier just to squash merge rather than give the contributor a lesson on reabse every single time. Naturally you shouldn't squash if the history needs to be cleaned up manually but it's rare to have multiple authors on one PR.
Re: GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
#30And squash merge is still an ee-only (paid-only) feature ¯\_(ツ)_/¯
What does this actually mean? Does their UI just fall apart if you force push after squashing in git rebase -i?
actually they always merge via -no-ff.
and time tracking in issue's is also a ee only thing.
actually the last releases were pretty much focused on ee-only stuff, it's sad that it will be more closed caused by the money.