I’ve been a longtime advocate of . These templates allow you to provide instructions to developers creating pull requests in your repos so that they will be reminded to include all the relevant information you need to properly review their code. Pull request templates are a great place to include as additional reminders. These might include to-dos like remembering to write unit tests, self-reviewing your code, or doing a security audit. pull request templates checklists Sometimes though, these checklists can get long. You may have so many important items that developers begin to ignore them. Or perhaps some of the checklist items are only relevant in specific situations or when certain files are changed. While each item is important, they may not all always be applicable. Wouldn’t it be nice if your pull request checklists could be dynamic and only show relevant reminders? CodeSee Code Automation can help you do just that! With Code Automation, you can configure rule-based triggers to automatically add checklist comments to the pull request when certain conditions are met. In this article, we’ll look at some of CodeSee’s Code Automation templates and show how we can incorporate one of them into a codebase of our own. Ready to get started? Automation Templates There are several different on the CodeSee site that we can use as our inspiration. For example, there are checklists for , , , or . automation templates adding icons creating a migration adding a new npm package creating a new API endpoint For our demo, we’ll explore the icon checklist and modify it to meet our needs. Our Fictional Icon Repo Screenshot of our demo icon library containing hundreds of icons for developers at our company. When a developer needs a new icon not found in our icon library, they talk to a designer, and the designer creates an SVG file for the developer. The developer then takes the SVG file and adds it to the code repo. Let’s imagine that we have a repo Simple enough, right? The problem is that the SVG file from the designer is often messy. Usually these files will have random ID attributes included. There might be extra comments or unnecessary code in the file. The file name will probably not follow the same pattern as the other icon files. And, there might be additional code setup needed besides simply committing the new SVG file. The developer may need to update a master list where the icons are exported or update some documentation or Storybook examples. Some developers might just add the SVG file without giving any of these additional steps any thought. The solution, then, is to have a checklist that reminds developers what they need to do when adding a new icon. This checklist could exist in a README or in a pull request template, and I’d highly recommend you do both of these things. But even then, developers sometimes just don’t read the docs. They ignore the instructions and blindly press forward. To solve this, let’s add a Code Automation Trigger so that the developer is freshly reminded with a checklist comment when they create their pull request. Adding the Icon Checklist Automation Template To begin, we’ll first need to give CodeSee access to our GitHub repo from the Settings page. Connect CodeSee to your GitHub repo Once our repo is added, we can navigate to the Automate page to create our first Trigger. Add your first Trigger We’ll click the button to access the New Trigger page. Add Trigger New Trigger page On this page, we can add a name and repo to our Trigger and then specify the conditions and the actions. In our case, we want the condition to be whenever a new file is added to the directory. src/icons Add Conditions for your Trigger When that condition is met, we want CodeSee to automatically comment on the pull request with a few checklist items. We’ve added three items here, but you can add as many items as you’d like. Add Actions for your Trigger After we’re done editing, we can click the Save button to save our changes. With that, we’ve just created our first dynamic checklist! Let’s see this automation in action. In our code repo, let’s add a new SVG file to the directory. Then let’s create a new branch and submit a pull request to merge our branch into the master branch. src/icons Once our pull request is created, you’ll notice that the CodeSee bot automatically comments on our pull request with a checklist of reminders. Good thing too, because we forgot to do these things! The CodeSee bot has added a comment on the pull request Conclusion That’s it! In just a few short minutes, we’ve added a checklist to help our developers have a better experience when adding icons. We’ve made code expectations clear and highlighted possible items that the developer may have missed. And, best of all, we’ve added these comments dynamically, only showing them when actually needed. If a developer were to make a different contribution to this repo that didn’t involve adding a new icon, they wouldn’t see these comments at all. The cool thing is that this is just the start. We can add all sorts of other automation templates to our repo. And, these Triggers can do more than just add checklist comments. They also allow you to automatically assign reviewers to the pull request in the event that the expertise of certain developers or teams is needed. With CodeSee Code Automation, we can enforce best practices and share knowledge effortlessly. Also Published Here

Different

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

How to Use CodeSee's Code Automation to Create Dynamic Code Review Checklists

Too Long; Didn't Read

Companies Mentioned

Tyler Hawkins

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

How to Use CodeSee's Code Automation to Create Dynamic Code Review Checklists

Too Long; Didn't Read

Companies Mentioned

Tyler Hawkins

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES