Live data from Hacker News

GitLab 8.11 Released with Issue Boards and Merge Conflict Resolution

about.gitlab.com

31–40 of 128 posts

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

#32
post #15

Congrats to the Gitlab team for pushing this out the door so quickly! 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! [1] htt…

Totally agree with the single source of truth. I think ZenHub is very well done.

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

#33

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't have to compromise features or usability when opting for the free software alternative.

I was considering going self-hosted too, but then gitlab.com got a lot faster (thanks!!)

Glad to hear you're noticing the speed. We still have a lot of improvements in the pipeline. https://gitlab.com/gitlab-com/infrastructure/issues/59 We now host 2 repo's on Ceph, we'll move GitLab CE shortly and transition all the rest after that. https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

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

#34
post #27
post #7

Earlier quoted context omitted.

New features look awesome. Any idea of when we'll get global search? For a long time I've been wanting to search for a particular code snippet or file name across all projects.

Thanks! Isn't that global search possible with Elastic Search http://docs.gitlab.com/ee/integration/elasticsearch.html (EE only)?

Oh, possibly. I don't actually use EE, but I just assumed it was still unimplemented because the issue is still open:

https://gitlab.com/gitlab-org/gitlab-ee/issues/556

Edit: looks like they updated this issue since I last checked and the feature is scheduled for `8.12`

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

#35

Another excellent Gitlab release -- I'm super excited to hear about the addition of issue boards. Please replace Jira and github at the same time. I <3 Gitlab

I hope this is the intention. I'd love to migrate off Jira. Presumably like others, it's the reporting and accounting features for management purposes that have kept us tied to it.

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

#36
I'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've found GitLab's integrated toolset to be superior to what GitHub currently offers, and in truth there isn't really anything I feel like I've been missing (some tools like Code Climate are only free for GitHub accounts, but it's easily resolved by just using both).

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.

Setting up a project for both just takes a few initial commands to configure git:

  git remote set-url --add --push origin git@github.com:account/repo.git
  git remote set-url --add --push origin git@gitlab.com:account/repo.git
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.

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

#37
post #36

I'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've found GitLab's integrated toolset to be superior to what GitHub currently offers, and in truth there isn't really anything I feel like I've been missing (some tools like Code Climate are only free for GitHub accounts, but it's easily resolved by j…

> some tools like Code Climate are only free for GitHub accounts, but it's easily resolved by just using both

Are you doing a read only mirror to GitHub for this?

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

#39
post #31

What's the reasoning behind the different characters in slash commands? # Why /milestone %milestone /label ~foo # Instead of /milestone milestone /label foo

Both of those formats also work in comments outside of slash commands, are automatically linked to the respective entity, and label references are rendered as pretty labels, with their color and description tooltip.

Using those characters also enables autocomplete in the Markdown textarea.

In the web interface, they are very convenient, but they are not required, so when using slash commands with reply-by-email, you can leave them out and write exactly what you have under "Instead of"

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

#40

We're super proud of this release. As always, we're here for any questions or comments.

The issue boards are a big deal, so congrats on getting that out! I've said this before, but one huge thing you guys could do that would draw in a lot of companies to Gitlab EE is if you supported custom issue fields [1][2] with various field types. That feels like a pretty logical place to go from here, so I hope you guys are strongly considering it. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/8988 [2] https:…

Agreed, custom fields is where the pinch point is for most companies I contract at.
Post reply on HN