As a chat service, it's important for CodeStream to make sure that you're aware of new messages from your teammates, but at the same time give you the controls to determine how and when you're notified. Here's what we've got so far...
Source Tree Indicators
Since the source tree in your IDE is now effectively a list of chat streams, it makes sense that this is where you'll find out about new messages. Right-click on any filename in the source tree and look for the Notifications sub-menu to see the options CodeStream gives you for how you'll be notified about new messages.
- Badge - By default, new messages are indicated by a file name displayed in bold along with a gray badge with the total count of new messages in the file. If you've been mentioned in the file, the gray badge will be replaced by a blue badge, now showing just the count of the number of mentions instead of the total number of unread messages.
- Bold - If you don't want to be distracted by the number of unread messages in each source file, but still want to know when there are unread messages, select this option and the file name will be displayed in bold but no badge will be displayed. If you've been mentioned in the file, however, a blue badge will also be displayed with a count of the number of mentions.
- Mute - Select this option if you don't want to participate at all in discussions about the given file. There will be no indication of new messages for muted files, and importantly, no email notifications will be sent. Note, though, that if you are mentioned in the file, a blue badge will still be displayed and, depending on your settings, an email will be sent. In other words, a mention overrides the mute selection.
You'll notice that the Bold, Badge and Mute options are available for each file and directory at every level of your source tree. If one of the above options hasn't been explicitly selected for a given file or directory, we'll work our way up the tree until we hit a file/directory with a selection, and use that, otherwise we just fall back to the Badge option.
If you want to change the default setting, without having to change the selection for the top-level files and directories across all of your repositories, go to the settings for the CodeStream plugin. In Atom, select Preferences, and then click the Settings button in the CodeStream entry.
Some repositories can be quite large, with hundreds of files and directories, which means that some files with unread messages may not be currently in view in your source tree. When this happens, a message will be displayed at the top/bottom of the left pane to let you know that there are unread messages above/below. In the example below, the indicator is blue because you were mentioned in the unread messages.
Email notifications are sent when you are explicitly mentioned in a message and you meet one of the following criteria:
- You don't have your IDE open.
- The messages were posted to a repository that you don't currently have open in your IDE.
- You've been invited to join a team on CodeStream, but haven't yet signed up.
You can even reply to email notifications, and the replies will get posted to the appropriate stream.
Note that settings to manage your email notifications are coming soon. In the meantime, if you'd like to turn off emails just contact our support team at [email protected].
Set up the Slack integration and all of your team’s messages on CodeStream will flow through to the channel of your choice on Slack. You can even reply to those messages right from Slack, and the replies will get posted to CodeStream. A great option for teams that have developers using IDEs not currently supported by CodeStream.
To set up the Slack integration, go to Atom’s command palette (under the Packages menu) and search for “Codestream: Slack Integration”. Note that the integration only needs to be set up by one person on your team. No need for everyone to set it up individually.
In addition to more controls over these notifications, also on the way are configurable desktop notifications, sounds, and a “heads down” mode.