|
|
Subscribe / Log in / New account

New CPython workflow issues

New CPython workflow issues

Posted May 29, 2017 19:29 UTC (Mon) by dag- (guest, #30207)
In reply to: New CPython workflow issues by darwish
Parent article: New CPython workflow issues

This may all be true, and once GitHub had no real competition in this area. But GitLab is now feature-complete and exceeds GitHub in many aspects. My remark related to convenience was more about what people already know (mindshare) rather than real convenience, as in "efficiency".

And having used both extensively, GitHub in the community and GitLab at various companies. There is a clear benefit to work with an Open Source project (to which one can troubleshoot and contribute) over a hosted service offering (with weird incomplete workflows and suboptimal implementations).

I am not saying GitLab is perfect, but at least everything that's bothering you that much, you can dive in and fix it yourself. (Which I also did a few times) I would even say that some of the stuff that people now do in bots should move back into GitLab workflows when the time is right and there's general consensus. With GitHub we have been waiting for years for something to be fixed, or some feature to appear (like issue/PR templates). GitHub's review workflow is completely broken by design...


to post comments

New CPython workflow issues

Posted Jul 6, 2017 3:24 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

What's wrong with GitHub's review in your view? I prefer parts from each (I wish GitHub had resolvable subthreads and Gitlab had batch code comments), but prefer Gitlab overall. I do review much more code with Gitlab though, so maybe it's just a difference in scale.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds