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

41–50 of 128 posts

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

#41

Post by DouweM »

superice wrote: post #11

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't need this when you can restrict branch access to a spec…

CE does support restricting branches to specific roles: Master and Developer. In your case, I would suggest giving this single maintainer the Master role (which they already have if they're the owner of the project), making everyone else a Developer and configuring the master branch to only allow pushes (and merges) from Masters.

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

#43

Post by dak1 »

tedmiston wrote: post #37
dak1 wrote: 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?

Effectively. My project still gets pushed to GitHub and lives there, but I've disabled every feature I could (you can't disable PRs, but it's easy enough to redirect PRs over to GitLab).

Code Climate can still happily read from the GitHub project and I can add the badge to the README if desired, which is visible on both GitLab and GitHub.

And since origin pushes to both, they are rarely if ever out of sync.

And by using GitLab I get GitLab CI instead of Travis (which is quite nice), GitLab's amazing Issue tracker and board, which blows GitHub away, more fine grained control over merging (no more forced --no-ff merges if you don't want), Issue and MR templates, an activity stream, far more control over your project's settings... really I can't say enough good things about my experience with GitLab over the last ~6 months.

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

#45

Post by sinatra »

sytse wrote: post #24
sinatra wrote: post #21

Earlier quoted context omitted.

Since using Asana, one feature I want in every project management / issue management tool is the @mention [0]. Asana's @mention allows you to link other tasks or issues very conveniently. Just like HipChat's commands feature mentioned in your release notes, Asana's @mention feature is extremely convenient. [0]: https://asana.com/guide/help/fundamentals/text

In GitLab you can use @ to mention people, # to mention issues, and ! to mention merge requests.

Great! Thank you for letting me know. Any chance of supporting something like that for the wiki pages too? So that we can refer to other pages or headers in those pages using @ or # mentions?

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

#46

Post by DouweM »

dak1 wrote: post #43
tedmiston wrote: post #37

Earlier quoted context omitted.

> 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?

Effectively. My project still gets pushed to GitHub and lives there, but I've disabled every feature I could (you can't disable PRs, but it's easy enough to redirect PRs over to GitLab). Code Climate can still happily read from the GitHub project and I can add the badge to the README if desired, which is visible on both GitLab and GitHub. And since origin pushes to both, they are rarely if ever out of sync. And by us…

GitLab can actually keep your GitLab and GitHub repos in sync automatically! Check out the "Mirror Repository > Push to a remote repository" option in your project's settings.

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

#47

Post by unethical_ban »

qznc wrote: post #18

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). 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? R…

The visualization and instant-modification of kanban boards is really appealing from a task/issue management perspective. It shouldn't replace issue tracking, it can serve as a frontend to portions of it.

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

#48

Post by kolanos »

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 needed (and would be appreciated) it's accessibility. Happy to help on this front, but I know for a fact there's already several open issues relating to accessibility for GitLab.
Post reply on HN