Build the knowledge base behind your codebase. CodeStream allows your development team to communicate within Atom and conversation threads automatically become annotations that live with your codebase forever.
CodeStream is currently in beta. The core messaging functionality, which is the heart of the service, is there and ready for you to use. Some other components of the service are still in the works.
gitavailable in their PATH.
To install CodeStream, visit Atom settings, click on the "Install" tab in the left rail, and then search for 'codestream'. When you find it in the results, click the 'Install' button.
Once installed, you can toggle the CodeStream view via the Packages menu, or hit Cmd + Opt + O (Mac) / Ctrl + Alt + O (Windows). You can also click on the chat bubbles icon that now appears in the status bar at the bottom of the Atom window.
Select a file in your source tree and you’ll see a chat stream in a new pane on the right. In fact, each source file has its own contextual chat stream.
To talk about a specific block of code, just select the code in your buffer and then click on the “+” button that appears.
Your team’s message history is stored in the cloud on CodeStream’s servers. Note that CodeStream does not store a copy of your source files. When a message includes a code block, a copy of that block is also stored in the cloud, but not the entirety of the source file.
All of your team's messages are also stored locally on your computer, meaning that you'll even have access to the message history when you're offline.
In addition to people that you explicitly add to your team on CodeStream, anyone with access to the codebase may join the team on their own. To do so, they will need to sign into CodeStream with the given repository (as identified by the URL of the origin and the hash of the first commit ID) open in their IDE.
On CodeStream, chat streams are associated with source files, and not with commits. This allows developers to easily leverage past discussions to get a better understanding of how the file evolved over time and why specific changes were made. A new developer inheriting one of your files a year from now will never go back and reference past commits or pull requests, but on CodeStream they’ll see both the entirety of the chat stream associated with the file as well as markers in the code indicating where discussions took place.
CodeStream recognizes that developers on your team may be working on different branches, or may simply have local changes, that result in certain blocks of code being in different locations for each of them. If there are messages associated with those blocks of code, CodeStream ensures that each developer sees them in the correct location despite the variations in each of their local buffers.
You won’t need to provide CodeStream with any Git (or GitHub, Bitbucket, etc.) credentials, as the plugin simply leverages your IDE’s access to Git. CodeStream uses Git to do things like automatically mention the most recent author when you share a block of code in a post, and to maintain the connection between that block of code and where it’s located in the source file as the file evolves over time (and commits).
Check out our help site for more information on getting started with CodeStream.
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.