The CodeStream Blog

Code reviews provide a great forum to provide feedback, but all too often development teams focus on providing the best technical guidance while ignoring the human side of the feedback process. Code reviews can be a great opportunity for software development teams to learn, mentor and collaborate with one another. However, they can quickly become roadblocks if colleagues are not thoughtful with one another in how they communicate feedback during the code review process. 

In Part 1 of this series we touched on the evolution of IDE from a personal, standalone tool to a connected and networked hub of all things code. We explained how connecting your IDE to your teammates’ simplifies communication and collaboration with two specific use cases: Discussing code in general, and performing code reviews right in your IDE, eliminating the context switching and improving knowledge sharing.In this post we will expand this to additional use cases and show how the Connected IDE is the most important step towards team collaboration in a world where we are all remote developers.

As the team became larger, important conversations about the code were scattered across their various development tools and systems. It was becoming increasingly common for team members to misunderstand a key decision because they could only see part of the discussion, or altogether miss key conversations and information exchanges. They needed a solution to consolidate team communication and make information about the code readily accessible to all team members. Enter CodeStream.

A new era of connected IDEs is coming that does not require you to leave behind the IDE you love. Using modern plug-in technologies, your IDE can begin to evolve towards a truly Integrated Development Environment that will make collaboration easier while improving code quality.

We have received many requests for the ability to have multiple reviewers approve a code review, and not just whoever did it first. In addition to accommodating that request, we’ve also added a number of options for how reviewers get assigned.

GitHub Enterprise (GHE) and GitLab Self-Managed (GLSM). New integrations address security roadblocks: If your integrations are not set to a publicly addressable URL, you can now access them by leveraging personal access tokens to eliminate that requirement.