GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

GitLab keeps surprising me with the consistency and quality of their releases. They are really putting GitHub on the spot at the moment and I for one love the competition in this space

I&#x27;ve recently moved to pushing all my open source code to both GitLab and GitHub, but using GitLab for actual issue tracking, continuous integration, build tests, etc. I&#x27;ve found GitLab&#x27;s integrated toolset to be superior to what GitHub currently offers, and in truth there isn&#x27;t really anything I feel like I&#x27;ve been missing (some tools like Code Climate are only free for GitHub accounts, but it&#x27;s easily resolved by just using both).<p>Plus the GitLab team has just been killing it with each release, and it just feels good to use open source (and be able to open issues, vote on improvements, track changes for the upcoming release...). Free private repos is just icing.<p>Setting up a project for both just takes a few initial commands to configure git:<p><pre><code> git remote set-url --add --push origin git@github.com:account&#x2F;repo.git git remote set-url --add --push origin git@gitlab.com:account&#x2F;repo.git </code></pre> Then pushing to origin will always push to both. I also add a github and gitlab remote in case I only want to push to one as well.

Congrats on the release. Haven&#x27;t tested this version, but have tried recent versions and if there&#x27;s one thing that I think GitHub still runs circles around GitLab it&#x27;s accessibility. If you don&#x27;t believe me, try firing up a screen reader and see which you find easier to navigate with your eyes closed. In some cases you&#x27;ll run smack into a brick wall with GitLab. So if there&#x27;s one area where massive improvement is needed (and would be appreciated) it&#x27;s accessibility. Happy to help on this front, but I know for a fact there&#x27;s already several open issues relating to accessibility for GitLab.

We&#x27;re super proud of this release. As always, we&#x27;re here for any questions or comments.

The &quot;Gitlab doesn&#x27;t handle big commits&quot; bug is still a thing, and the two issues open for it are still open (and have been for months).<p>8.11 overhauled the diff backend, which works great! But the front-end still chokes up and freezes because the default appears to be 1000 files worth of diffs. This still pegs my CPU and hangs my browser when the page tries to render.<p>The second time loading the page is always fast (maybe something caches somewhere), but the first time is slow and chews the heck out of my poor PC. :(<p>Any chance we could get some sensible limits on the amount of information shown in a diff? Nobody is going to wade through 1000 files of diff in a web browser, so there&#x27;s no reason to jam things up trying to render it.<p><a href="https:&#x2F;&#x2F;gitlab.com&#x2F;nrclark&#x2F;dummy_project&#x2F;commit&#x2F;81ebdea5df2fb42e59257cb3eaad671a5c53ca36" rel="nofollow">https:&#x2F;&#x2F;gitlab.com&#x2F;nrclark&#x2F;dummy_project&#x2F;commit&#x2F;81ebdea5df2f...</a><p>edit: also, clicking the &quot;Plain Diff&quot; button breaks Gitlab

Is it a matter of taste or Github&#x27;s UI indeed looks more professional than Gitlab&#x27;s one? I&#x27;ve tried to switch from GH to GL hosted for my personal projects multiple times and no luck. I like the fact that Gitlab is open-source and it has a lot of features but I still don&#x27;t feel comfortable using it. Any opinions and preferences on GH&#x27;s UI vs. GL&#x27;s UI?

I migrated to using GitLab.com from GitHub for all of my publicly-hosted repos and use a self-hosted instance for some other projects as well. I love that I don&#x27;t have to compromise features or usability when opting for the free software alternative.

With both GitHub and gitlab, I wish there was more work in making it easy to create pull requests without having to click around on a website.<p>I&#x27;ll often check out software, notice something small that I can easily fix, and spend 5 minutes fixing and testing it. But then I have to spend another 5 minutes going on GitHub, forking the repository to my profile, going back into my shell, changing the URL for origin, pushing the change, going back to GitHub, creating the pull request on the project, and then going back to my profile and deleting the fork that I have no interest in maintaining. This should be so much easier.<p>That being said, I run Gitlab under a small docker box and I couldn&#x27;t be happier with it. It&#x27;s so darn easy to setup. Grats to gitlab team.

Another excellent Gitlab release -- I&#x27;m super excited to hear about the addition of issue boards. Please replace Jira and github at the same time.<p>I &lt;3 Gitlab

Congrats to the Gitlab team for pushing this out the door so quickly!<p>Back when we built one of ZenHub’s [1] first features — task boards inside GitHub — we believed strongly that development teams needed a single source of truth in order to move faster and communicate better. That belief has underscored everything we’ve built since. It’s awesome to see further validation for this philosophy here with Gitlab!<p>[1] <a href="https:&#x2F;&#x2F;www.zenhub.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.zenhub.com&#x2F;</a>

What&#x27;s the reasoning behind the different characters in slash commands?<p><pre><code> # Why &#x2F;milestone %milestone &#x2F;label ~foo # Instead of &#x2F;milestone milestone &#x2F;label foo</code></pre>

A tiny question: does this mean a workflow in which only one user would be able to merge a specific branch (say: master) is only available in the enterprise edition? I imagine this is quite a common workflow, even at smaller companies or non-profits. This essentially forces you to use an entire repo per user to do code review, even though oftentimes you wouldn&#x27;t need this when you can restrict branch access to a specific (set of) users.<p>For example, I&#x27;m active at a small non-profit computer shop at the campus of my university, and we develop our own stock managementsystem inhouse. This would be a very interesting feature even for non-enterprise users like us, because that&#x27;d allow for easy code reviews without having to fork the repo.

GitLab looks very tempting, congrats to their team.<p>Question: I would like to migrate from Github to Gitlab, but can not really move. Is there some bridge, which would mirror Github repos (with Issue tracker and pull requests) on Gitlab?

I have yet to understand where this kanban board stuff makes sense. Apparently, the Agile philosophy [0] introduced this to the software development world. Most implementations (Gitlab, Wekan) seem to miss central features (limits, cycle time stats).<p>I guess those boards serve as a issue tracker extension for short term development? How does that improve the process? Why do you need that on top of an issue tracker? Replacing the issue tracker is probably not idea?<p>[0] <a href="https:&#x2F;&#x2F;www.atlassian.com&#x2F;agile&#x2F;kanban" rel="nofollow">https:&#x2F;&#x2F;www.atlassian.com&#x2F;agile&#x2F;kanban</a>

Merge conflict resolution seems like something incredibly obvious to have, that yet is a pretty unique feature for the web UI. I&#x27;ve done a lot of stuff with GitHub&#x27;s web UI, and I pretty much hit a wall any time I do something that&#x27;s going to create a merge conflict, since I never really bothered to learn Git CLI. I saw GitBook did something similar to this a while ago, but that&#x27;s for books, not code.

I just migrated our companies repos away from Bitbucket to GitLab. The whole process was super-easy. Really happy so far!

Gitlab has a really great set of features and I appreciate the open and professional development style very much. It&#x27;s very resource-hungry, though. At one point I just gave up and switched to Gogs. Less features, sure, but very fast, even with many users.

My job would <i>never</i> cotton to putting stuff on Github, so GitLab existing and being of such high quality has been fantastic. Really been impressed with it.

This is great <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=UWsJ8tkHAa8" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=UWsJ8tkHAa8</a>

I&#x27;m seeing this as Gitlab working towards their Jira killer. With Mattermost also in the omnibus edition this is rather ace. Congratulations to the team!

congrats for the new release, here my critic (don&#x27;t take me wrong, I use and love gitlab for so long, and the other features of 8.11 are really awesome)<p>* merge conflict resolution: It definitely looks cool and make conflict resolution <i>BY MERGING</i> easier than any other way i know BUT most of the time I want my co-worker to resolve conflict BY REBASING (i.e as if they had branched just right now) , following the principle that you merge from specific to generic. So though I definitely agree most of people don&#x27;t care, but for larger team&#x2F;project where you often need to make archeology and dig inside the commit history , the &quot;master merged into feature branch&quot; makes the commits tree look weird<p>Outside of this, it&#x27;s maybe only me, but most of the team I&#x27;ve worker with where using a scrum-like taskboard (like <a href="http:&#x2F;&#x2F;taiga.io" rel="nofollow">http:&#x2F;&#x2F;taiga.io</a> ) instead of a kanban-like, is it planned to be added&#x2F;provide the option or (which I perfectly understand) do you plan on focusing on kanban and letting third-party project for those who prefer scrum ?

Shouldn&#x27;t the video start with &quot;We make software by turning issues into ideas&quot;, not the other way around?<p>We&#x27;re always trying to promote this idea of &quot;don&#x27;t sell the product, sell the problem you&#x27;re solving&quot; and your opening statement completely tips that on its head.<p>Not knocking GitLab in any way, I love your product and have used it for a while. Amazing work. Just me being a pedant ;)

I&#x27;m glad there&#x27;s starting to be a good amount of choice in this realm of tools!<p>I&#x27;ve actually just lately been looking into a new all-in-one package like this for our company. Git hosting, code reviews, issue tracking, wiki, and nice project management features all in one place. My current systems-under-test are Phabricator and Jira.<p>Anyone have an opinion on how GitLab compares to those two?

So excited for this release! These guys are killing it on features!<p>Also noticed the speed&#x2F;performance improvements lately.<p>Great job, GitLab!

Awesome! Really awesome features. Time to persuade my boss to move to Gitlab now.<p>Just need some data on the latency and reliability. so far, I only found <a href="https:&#x2F;&#x2F;status.gitlab.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;status.gitlab.com&#x2F;</a>. need some historical data now.

This is awesome. Is it possible to have a central set of issues per group? Many (real-world) projects have issues that span across multiple (GitLab) projects. I guess one could create an &quot;empty&quot; project for issues, but this is hacky. Thanks again.

My first impression of the Issue Boards is that it reminds me of Trello quite a bit! I happen to like Trello, and whether or not this new feature was Trello-inspired I&#x27;m excited to give it a test run.

How do we use the mattermost features on gitlab.com ?

An awesome release! Waiting for Koding to be enabled on gitlab.com ..

GitLab&#x27;s been going at it for quite a while now, congrats for another awesome release! And keep up the great work guys, it&#x27;s much appreciated!

Anyone notice that Github is getting dog slow lately? When browsing source trees it used to be lightning fast. They&#x27;re trippin&#x27;.