Slack Review Channels

Reviewing code requires a lot of back-and-forth between platforms and multiple chats. Developers communicate on both GitHub and Slack which causes constant context-switching whenever attention is needed ("Hey, did you see my comment on GitHub?"), and have to manually coordinate the pull request with all different collaborators.

Moreover, collaborators need to check their emails or their GitHub notifications to get updated with the current status of the pull request.

This workflow introduces a lot of idle time to the asynchronous nature of code reviews as every new comment requires to -

• Ping the reviewer (or wait until the reviewer sees the new comment on GitHub)

• Waiting for the reviewer to finish his task to be able to context-switch to GitHub

• Waiting to get pinged back that the reviewer replied (or stumble across the new comment when they open their email)

• Switching back and forth until no more comments are added

• Pinging more reviewers, updating them with the current status of the PR and all the latest discussions

This inefficient workflow translates to an average of two days of idle time for every single chunk of work.

This extended code review period also raises the chance of reviewers losing important context simply by forgetting it. Code reviews accompanied by extended idle time lead to lower-quality reviews and a decrease in engineering output, causing delays in project delivery.

Typical pull request review workflow

devoro counters this issue by centralizing all PR communication into a Slack channel, with all collaborators automatically invited. This brings your code reviews workflow directly to Slack, making it easy to discuss and increasing the responsiveness of your team on every new pull request.

Instead of having to context switch to Github, add a comment, and ping the developer/reviewer manually, devoro utilizes the benefit of the instant messaging workflow your team already uses.

How it works

• devoro opens a Slack channel with all collaborators invited for each pull request

• All comments on GitHub will be posted to the Slack channel by the devoro-bot, mentioning who authored them

• All discussions in the channel will be synced back to GitHub's pull request

• PRs are automatically archived when the PR is merged or closed

devoro's review channel

The benefits

• Collaborators get updated immediately when a new comment is added to the pull request

• Collaborators are more responsive in the review process as they can discuss directly on Slack

• Developers don't spend time manually coordinating their pull requests across multiple DMs, channels, and platforms to get approvals

• Pull request reviews are resolved faster

• Pull request collaboration is streamlined and efficient

Improve your collaboration and merge faster for free ->