Hi Ola, thank you for the reply. Are there any annoying or inconvenient parts of this process that you don't like. For example - do you need to remind others about reviewing a PR? Can you forget about a small PR being reviewed and ready to be merged? Or, for example, someone giving you a review before CI fails and then you need to request a review again? Thank you!

Hi Astha, thank you for such detailed answer! It looks like the described flow works quite well for you. Is there any part of the process that you find inconvenient or annoying? I've never used MS Teams so it's hard for me to understand some of the specifics. Hope you don't mind a couple clarifying questions: Once we create PR, notification goes to both the teams "ABC" and "XYZ" via email or we copy the link and send it to respective developer for review and approval of PR. Does it always work well for you? Do you ever need to remind people about reviewing a PR? Does that "PR email" ever get lost between other mail people receive. Does MS Teams send these notification automatically? Once the approval is done, there will be a green tick mark on both the teams name that your PR is approved. Is this green marking a feature of MS Teams product? Thank you!

Asad Awadia Thank you for the feedback! It's quite interesting you mentioned simplified setup. The original idea was to appeal to companies where multiple teams work on the same repos. For this case it makes sense to have a dashboard per team, so there's no way to remove the concept of teams from PRBoard, but there's a default dashboard and a team created for you right after you install PRBoard. You're absolutely right - it's in the pullpanda (now GitHub) space, but we found that sending notifications to Slack might not be enough in terms of advanced features - it's hard to see high-level picture of what PRs are there and their state, especially if your team works across multiple repos. The same goes for knowing which PRs are ready to be merged when they're approved and all checks pass. We're also going to add "heated comments" and "stale" PR properties to indicate a large number of comments on a PR, and its age. Do you think any of those features might convince you or people you know to try PRBoard? Thank you for your feedback!

Hi Asad, thank you! Yep, did all of the design myself in ReactJS and Tachyons. It's actually a very high praise for me since I'm quite far from being a designer :) What do you think about the idea? How do you work with pull requests in your team?