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.