The CodeStream Blog

Many discussions about code involve more than just one block of code, and concepts are often best presented when you can refer to multiple code locations at once. CodeStream’s latest release introduces multi-range codemarks that address exactly those scenarios.

CodeStream now displays merged Pull Request comments in your editor as annotations on the current version of your file. By integrating PR comments from GitHub and Bitbucket (and soon GitLab) with CodeStream’s native codemarks in a single view, developers will gain deeper insight into why decisions were made, and get answers faster to questions about code they are working on.

In Part I, we discussed specific suggestions to improve code reviews using PRs, and how the methodology itself has inherent limitations. In this post we review the suggestions made by Jonathan Maltz of Yelp in his article Code Review Guidelines. They are similar to many other articles you can find on the topic, so they serve as a clear outline for this discussion.

When you share a codemark with your team, they can access it in their messaging stream. CodeStream now allows them to view that codemark in context, whether in their IDE or in GitHub, GitLab or Bitbucket. They just click on the link that best suits their needs to view the information in context. With context, they will understand the question or issue faster, and be able to respond more effectively.

CodeStream 2.1 brings two powerful new features, CodeLinks and Tags, that further enhance your ability to discuss, review and understand information about your codebase. 

CodeStream is now available as an on-prem solution, meeting the needs of organizations and enterprises that require all tools or systems that touch their code to be hosted in their own internal environment. CodeStream On-Prem follows existing support for other on-prem solutions, such as GitHub Enterprise and Jira Server.