The latest articles on DEV Community by ivanbokii (@ivanbokii). https://dev.to/ivanbokii https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F383334%2F6b62dcd8-91c5-4c3c-8682-17c08263ec34.jpeg https://dev.to/ivanbokii en ivanbokii Sun, 24 May 2020 12:29:22 +0000 https://dev.to/ivanbokii/how-do-you-work-with-pull-requests-at-work-1oa4 https://dev.to/ivanbokii/how-do-you-work-with-pull-requests-at-work-1oa4 <p>Hello friends,</p> <p>I'm working on a small side-projects called PRBoard (<a href="https://prboard.dev">https://prboard.dev</a>). It's a dashboard for teams that host their repos on GitHub. I'm currently in the market-validation phase, and I think some of my assumptions on how this product can be helpful for teams are invalid. For this reason, I'm gathering different ways engineering teams work with pull requests.</p> <p>For example, in my team, when someone creates a new pull request, they send a message on Slack about it. We rarely use GitHub's built-in "assignees" and "reviewers" features because usually, it's more than one person who can review a pull request. When someone picks a PR, they usually leave an emoji on the original slack message signalling that they're starting the review.</p> <p>There's a couple of downsides to the described approach:</p> <ol> <li><p>No clear picture of all currently open PRs from my team. We structure code as one big monorepo with multiple teams working on separate code paths. This makes using GitHub's pull requests page almost impossible.</p></li> <li><p>No way to know when a pull request is ready to be reviewed. We have a CI pipeline running different checks for every PR. It makes little sense to review a pull request that hasn't passed all test yet since there might be failures and further changes to address them.</p></li> <li><p>There's no way for PR author to know when their pull request is ready to be merged</p></li> </ol> <p>How does this process work in your team and are you happy with it? What's the most annoying part of reviewing others pull requests?<br> Regards!</p> github productivity sideprojects ivanbokii Sun, 10 May 2020 17:33:12 +0000 https://dev.to/ivanbokii/feedback-request-pull-request-dashboard-side-project-1dno https://dev.to/ivanbokii/feedback-request-pull-request-dashboard-side-project-1dno <p>Hello Friends,</p> <p>I'm working on a small side project called PRBoard [<a href="https://prboard.dev">prboard.dev</a>]. It’s a live, instant dashboard for your team's pull requests. Each pull request is represented as a small card with different status messages.</p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s--ltmPI0WX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/jggqfwx6zpwxen80y5or.png" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--ltmPI0WX--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/jggqfwx6zpwxen80y5or.png" alt="Alt Text"></a></p> <p>I know, GitHub has standard means to notify your team about pull requests like assigning a reviewer or using a slack notification. Still, it's always hard to quickly see what pull requests are open and available for review as well as those that passed all the checks and ready to be merged.</p> <p>Would love to learn your thoughts about this project. Are you pleased with how your team discovers and notifies about pull requests? Would you use something like PRBoard? Maybe you have an idea of a killer feature for a pull request tool? I'd appreciate if you can share it with me!</p> <p>Thank you!</p> github productivity startup sideprojects