Thank you Sytse for your words, I do really appreciate them :) GitLab is a great product and we do think we can help to make it even better with Gitcolony!
No it's not :) In fact, we know that devs don't like emails, so we manage everything from our tool (plus integrations with Slack & Hipchat).
In addition, we know that emails don't work, so we want to create actionable items directly from Gitcolony, no more emails with a list of things to improve. Just create your TODOs and tickets while you review your code and notify those users that need to be involved!
I'm sorry that you are experiencing that issue, can you please send us an email to [email protected] so we can try to reproduce it and help you with that? Thanks! :)
Our fault, we need to update that name to "Virtual Pull Requests" (we renamed them on our last release).
The main idea is that you can have a "virtual" pull request since the moment you create the branch (you can set up to get it done automatically by Gitcolony). Basically, you have a PR before you even create a pull request, but it's just virtual because it doesn't exist on Github, it only exists within the boundaries of Gitcolony.
This makes visible your work so your team can review it from the get go, without the risk of merging it by mistake.
And whenever you want, you can convert it to a traditional PR just with one click :)
Thank you for the nice words! Yeah, that's intentionally, but we can definitely improve that! (Meanwhile you can enter using this url http://gitcolony.com/pricing)
Super interesting feedback, I super appreciate it :) Actually we are working now to manage the whole merge process and then CI + code review is our next item to tackle.
Interesting debate! We want to improve the code review process for collaborators. If we improve that process for collaborators, in the long term it will be better also for managers :)
That's definitely the idea! We want to run on top of Github/other git hosting solutions to be able to setup your own rules while being more flexible and better than Gerrit (we think that the commit by commit approach it's definitely not the most efficient one).
Since GitHub started to grow, pull requests became very popular for open source contributions. Now, companies are also using them to reinforce their internal code review process. We think this can work even better by building the next generation of pull requests, helping companies to improve their process.
Thank you for your feedback and nice words about the design. As I said in the previous comment, we will work on that video and will keep you posted about it! :)
Meanwhile, feel free to create a free account, I would love to hear your feedback.
I definitely agree with this (disclosure: I'm Gitcolony's founder). I think that PRs are a great start point but not the best way to review code in a company. I do believe they are great option for open source contributions but not the most efficient one for companies.
Pretty interesting! Besides static code analysis, do you use any tool to manage manual code review, functional testing and integrations with deployment and task/issues management tools?