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

GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

about.gitlab.com

Post reply on HN
Print view View original

81–90 of 128 posts

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#81

Post by rmetzler »

kolanos wrote: post #48

Congrats on the release. Haven't tested this version, but have tried recent versions and if there's one thing that I think GitHub still runs circles around GitLab it's accessibility. If you don'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'll run smack into a brick wall with GitLab. So if there's one area where massive improvement is nee…

Gitlab's in-project navigation recently changed, Everyone on my team was confused.

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#82

Post by sytse »

allan_s wrote: post #73

congrats for the new release, here my critic (don't take me wrong, I use and love gitlab for so long, and the other features of 8.11 are really awesome) * merge conflict resolution: It definitely looks cool and make conflict resolution BY MERGING 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 princi…

Hugo already mentioned the rebasing option in https://news.ycombinator.com/item?id=12339492

As for the Kanban board, as far as I can read in https://www.cprime.com/2015/02/3-differences-between-scrum-a... the only difference with a scrum board is that you can set a maximum number per list. Feel free to create a feature proposal for that, I've already heard that request before today.

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#83

Post by sytse »

rmetzler wrote: post #81
kolanos wrote: post #48

Congrats on the release. Haven't tested this version, but have tried recent versions and if there's one thing that I think GitHub still runs circles around GitLab it's accessibility. If you don'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'll run smack into a brick wall with GitLab. So if there's one area where massive improvement is nee…

Gitlab's in-project navigation recently changed, Everyone on my team was confused.

We know that navigation redesigns are confusing. But we want to keep iterating to make it better. We explained the reasoning behind the change in https://about.gitlab.com/2016/06/06/navigation-redesign/

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#84

Post by mweilgart »

KamiNuvini wrote: post #53
neuromute wrote: post #25

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

What made you pick Gitlab over Bitbucket? Both can be self-hosted, but I'm not sure yet which one to choose myself. We do use Jira/Confluence internally so we might want to stick within that ecosystem but I hear very good things about Gitlab. I believe both integrate well with Jira as well and support smartcommits. What were the advantages for you?

I've been using GitLab for almost a year and I love it. I tried BitBucket and found it confusing and counterintuitive—the UI is crowded, as is the UI for JIRA and Confluence. (Don't forget that GitLab replaces Bitbucket and JIRA and Confluence, and actually does even more than that.) https://about.gitlab.com/comparison/#gitlab-ceee-vs-bitbucke...

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#85

Post by mweilgart »

nickysielicki wrote: post #56

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. I'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, push…

You mean something like this? GitLab just added the feature; it looks like what you're asking for.

https://about.gitlab.com/2016/08/22/gitlab-8-11-released/#mr...

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#86

Post by allan_s »

sytse wrote: post #82
allan_s wrote: post #73

congrats for the new release, here my critic (don't take me wrong, I use and love gitlab for so long, and the other features of 8.11 are really awesome) * merge conflict resolution: It definitely looks cool and make conflict resolution BY MERGING 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 princi…

Hugo already mentioned the rebasing option in https://news.ycombinator.com/item?id=12339492 As for the Kanban board, as far as I can read in https://www.cprime.com/2015/02/3-differences-between-scrum-a... the only difference with a scrum board is that you can set a maximum number per list. Feel free to create a feature proposal for that, I've already heard that request before today.

hmm yes you're right, I was mislead by the name of each list on the blog post, it's true that nothing prevent me from naming each column "new" , "in progress" , "ready for qa", and "done" , my bad. this + burn down charts (like proposed in https://gitlab.com/gitlab-org/gitlab-ee/issues/91 ) would really start for us to make gitlab embrassing the full life-cycle of our products.

As for resolving conflict by merging, thanks I didn't know EEhad this feature.

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#87

Post by jschumacher »

KamiNuvini wrote: post #53
neuromute wrote: post #25

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

What made you pick Gitlab over Bitbucket? Both can be self-hosted, but I'm not sure yet which one to choose myself. We do use Jira/Confluence internally so we might want to stick within that ecosystem but I hear very good things about Gitlab. I believe both integrate well with Jira as well and support smartcommits. What were the advantages for you?

Great to hear you're already using JIRA and Confluence. Adding Bitbucket to the mix will give you access to a bunch of great integration features.

We've been working on making it easier for the entire development team to collaborate and give them the right information at the right time. Here is a selection of features that I think you will find useful:

JIRA's Release Hub, to let you know if you're ready to release or not: http://blogs.atlassian.com/2015/04/jira-6-4-release-confiden...

The development panel, to turn every issue into a dashboard for it's development work: http://blogs.atlassian.com/2014/03/visualize-development-jir...

Automated issue transitioning, because it's easy to forget to move that issue to "In Review": http://blogs.atlassian.com/2014/08/jira-6-3-untangle-develop...

Hope this helps. For a good overview, you can also take a look at the documentation that outlines the above integrations: https://confluence.atlassian.com/display/BitbucketServer/JIR...

Re: GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

#88

Post by sytse »

allan_s wrote: post #86
sytse wrote: post #82

Earlier quoted context omitted.

Hugo already mentioned the rebasing option in https://news.ycombinator.com/item?id=12339492 As for the Kanban board, as far as I can read in https://www.cprime.com/2015/02/3-differences-between-scrum-a... the only difference with a scrum board is that you can set a maximum number per list. Feel free to create a feature proposal for that, I've already heard that request before today.

hmm yes you're right, I was mislead by the name of each list on the blog post, it's true that nothing prevent me from naming each column "new" , "in progress" , "ready for qa", and "done" , my bad. this + burn down charts (like proposed in https://gitlab.com/gitlab-org/gitlab-ee/issues/91 ) would really start for us to make gitlab embrassing the full life-cycle of our products. As for resolving conflict by merging, t…

Cool, thanks for asking and glad to learn we're on the right path.
Post reply on HN