Context
Software Engineering teams often share manually their Pull Requests to a Slack channel seeking a code review. This would not only speed up the review process but also boost productivity, increase team collaboration work visibility.
A year ago I got tired of copy pasting the PR info into Slack, and not being able to see its status with a quick look. prbot was born as a Hackathon to solve this issue. It ended up being used and loved by most of engineers at work.
I really enjoyed working on it so I decided to improve it and make it a product to keep coding cool and useful features around it.
Product
Even though the initial idea was simple, it kept evolving to what it is now:
Today's prbot mission is to enhance and speed up code review process, by automating Pull Request sharing, keep them in sync, and much more.
Features
- Automatic Slack message
- Synced Pull Request Status
- Synced Reviews Status
- Multiple Channel Support
- Customizable Message Format
- Advanced Settings
Configuration
Your config is a yaml file that you can put anywhere.
slack:
defaultChannelID: "00000000000"
repositories:
backend:
channelID: "00000000000"
front-end:
channelID: "00000000000"
messageFormat:
showSizeEmoji: true
Next Steps
I'm exited about the upcoming features like reminders, codeowners suppot, Microsoft Teams support, etc. However, they won't matter if you won't use it so I would love to know the features you would like to see in the prbot next releases.
How's your code review workflow? Tell me about it!
Happy coding!
Top comments (0)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.