![]() ![]() Now you're ready to go! How to Build the Pull Request Checklist AutomationĪlright, you're all set. You'll be prompted to install the PixieBrix Chrome Extension. Just select "Start for Free" on their website, and follow the wizard to create an account. In order to create the automation that I describe below, you'll need to sign up for a free PixieBrix account. The result? You get the productive, personalized experience you need. PixieBrix offers the most versatile low-code platform for extending the web applications you and your teams already use. ![]() There are a handful of browser extensions that let you create automations, but I've found PixieBrix to be extremely powerful and the community is friendly and helpful. Create a PixieBrix account (your browser automation tool) ![]() If you're still not sure, talk to more senior developers on your team and see what they are looking for when they review pull requests. Added any comments to make new functions clearer.Did I explain all possible solutions and why I chose the one I did?.Did I use the clear and concise names for variables and functions?.No unintentional console.logs left behind after debugging.If any new text is added, it's internationalized.Screenshot of the feature/bug fix (if applicable).Instructions for how reviewers can test the code locally.If you need some ideas, here is what I've incorporated in my own list. What makes it easy for you to review other pull requests? Or what's a common mistake you often find people commenting on? for a few minutes, think about what makes a good pull request, and list those items out. Make a list of what to check in your codeįorget any tools or any automation. Grab Your Toolsīefore you get started, you'll want to get a few things together. This tutorial shows you how to build an extension in your browser that will automatically generate a pull request checklist and hide the Create Pull Request button until you check every item on that list. I found a way to automate a PR checklist and force myself to do the work! I am particularly susceptible to opening a lazy pull request, so I did what any developer would do. At best, finding those tiny nits can take up other team members' time to notice and point out. But sometimes we miss the little things after a grueling coding session developing a new feature.Īt worst the, those mistakes can be missed by teammates and merged into the main codebase and create bugs or inefficiencies. We use pull requests to ensure only quality code is merged into our main branches. This requests that your code changes to merged into the main codebase. If you've ever contributed to a project, whether it's your app at work or an open-source tool, you've likely created a pull request. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |