Skip to content

Reviewing the Code Review, Part I

Claudio Pinkus on August 08, 2019

Some of our customers are telling us that they are using CodeStream to shorten code reviews by as much as 50%. It’s a lightweight approach, and we... [Read Full]
markdown guide

I watched the demo on your site, and that's pretty slick. Speaking as a remote worker for some 5+ years, I love the automation of tools I use anyway (Trello, Github, Slack, etc), but while keeping their asynchronous nature intact.


I agree that keeping the tools you love is the right way to go. That is why we integrate with those tools to allow everyone to get the benefits of real time collaboration with the workflows they already know. You can check out our integration with Trello here:


That's cool! What happens if someone deletes the Trello card? (I'm curious about this from a shop perspective, because I've written/maintained systems that integrate with Trello via their API)

CodeStream will still keep the issue codemark even if the Trello card is deleted. You can just archive it if it's no longer relevant, but the history remains.


Great points, for sure!

I agree that PRs and code reviews really be supported by IDEs more readily. Although timing is certainly the reason for the state of things, it doesn't follow that it need stay that way.

Of course, in a perfect world, code review would be inherent to the VCS itself, not to the version control host, in which case integrating into any IDE would be trivial.

If only...


We believe we have a solution that addresses all of these issues, including the integration with git itself. And totally agree that things don't have to stay this way. There are better approaches to try and experiment with.

code of conduct - report abuse