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

121–128 of 128 posts

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

#121

Post by sytse »

gsmethells wrote: post #116
sytse wrote: post #23

Earlier quoted context omitted.

It complements the existing issue tracker, the issues and the labels are the same. You can use issues without the board but it might be useful to give a visual overview. In meetings it is frequently easier to use a board see the many issue at a glance and to drag and drop them. I'm not sure we want to have the software enforce limits, but I do agree that you don't want any list/column to become too long. Cycle time a…

I think it would useful if the admin could opt-in to have limits enforced. That is a central tenet of kanban methodology. While the default could be no limit, I don't see why self-limiting should be prevented. I can open an issue if you like. :)

Please do open an issue, thanks.

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

#122

Post by randx »

daxelrod wrote: post #113
sytse wrote: post #83

Earlier quoted context omitted.

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/

Almost all of the navigation redesign was excellent. The information hierarchy was made much clearer. The only thing that confuses me and my coworkers about the new design is the decision to hide the left navigation bar behind a hamburger menu by default. It's great that we can pin it open now, but why hide all of that useful navigation behind an ambiguous, easy to miss, unlabeled icon?

> but why hide all of that useful navigation behind an ambiguous, easy to miss, unlabeled icon?

Few reasons:

1. After redesign its possible to use application without sidebar for most of day-to-day tasks. I personally use sidebar 2-3 times per day while using GitLab whole day. Keeping it hidden by default allow me to focus on context and save screen space (really valuable on small laptop)

2. Both sidebar and project navigation visible at same time confused a lot of users. For example user clicked on sidebar "Issues" while they believed it will take them to project issues page.

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

#123

Post by sytse »

stp-ip wrote: post #119
Flimm wrote: post #117

Earlier quoted context omitted.

Fascinating. I'd understand why GitLab and Gogs might not be competing with each other, but why invest in Gogs? How does that benefit GitLabs the company?

Keep your friends close but your enemies closer. Joking aside. Most likely to get a foot in the door on competition and on git related features written in Go, which might supplement or replace parts of the infrastructure within Gitlab. They already use Go for the CI runner part and as a smart, Gitlab aware proxy.

We want to prevent a not invented here mindset. And we'll work on import export functionality. By the way, GitLab already uses GitLab Workhorse written in Go to do much of the heavy lifting. I would say it is more then a proxy. This project is unrelated to Gogs.

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

#124

Post by AaronBBrown »

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…

Have you tried `hub`? https://github.com/github/hub

    ~/src/bar (foo =)$ hub pull-request
    https://github.com/foo/bar/pull/5
There is also `hub fork` and others:

    These GitHub commands are provided by hub:

       pull-request   Open a pull request on GitHub
       fork           Make a fork of a remote repository on GitHub and add as remote
       create         Create this repository on GitHub and add GitHub as origin
       browse         Open a GitHub page in the default browser
       compare        Open a compare page on GitHub
       release        List or create releases (beta)
       issue          List or create issues (beta)
       ci-status      Show the CI status of a commit

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

#125

Post by sytse »

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?

Just wanted to mention that GitLab CE/EE have support for using JIRA http://docs.gitlab.com/ce/project_services/jira.html

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

#126

Post by sytse »

aban wrote: post #102
jobvandervoort wrote: post #90

Earlier quoted context omitted.

Thanks aban! Any feedback?

You guys are awesome! For my 2¢, it would be really great to see some "official" love for Haskell at GitLab :) E.g. having Haskell tools installed on shared runners would be pretty nice! I'm also curious to know the state of functional programming at GitLab. I know you guys mostly do Ruby, but would you be open to employees using functional languages or frameworks for work? (e.g. Elm, Elixir, Haskell and other exciti…

We used Haskell for a dependency of our Omnibus packages before but it turned out to be very hard to install on many platforms.

Anyway, we don't install any tools on shared runner, we recommend you use a docker image and/or the scripts to do that.

We mostly do Ruby for the web app and Go for the heavy lifting https://gitlab.com/gitlab-org/gitlab-workhorse/

Now that we plan to ship with Cog we need Elixir for the first time. Help with https://forum.mattermost.org/t/help-wanted-cog-integration-f... is appreciated.

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

#127

Post by gsmethells »

sytse wrote: post #121
gsmethells wrote: post #116

Earlier quoted context omitted.

I think it would useful if the admin could opt-in to have limits enforced. That is a central tenet of kanban methodology. While the default could be no limit, I don't see why self-limiting should be prevented. I can open an issue if you like. :)

Please do open an issue, thanks.

Done https://gitlab.com/gitlab-org/gitlab-ce/issues/21325

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

#128

Post by zegerjan »

DouweM wrote: post #66
skift wrote: post #64

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

Mattermost is not enabled on GitLab.com, in part because it's not prepared for multi-tenancy, and in part because it is shipped with the GitLab package specifically for people who want to have a self-hosted development and collaboration environment. If you're fine with using hosted tools, there are plenty of great hosted chat tools out there!

DouweM, it is possible though to do this. Although a good seamless integration would require some extra work from our end. I've proposed this in an issue[1]. It is not planned though, at this time.

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

Post reply on HN