In theory, automatically finding recurring implicit anti-patterns would help improve the efficiency of code review. When we asked developers about creating rules for implicit anti-patterns, a frequent issue we often hear is that they can’t come up with any. What makes it difficult to find implicit patterns? …

2019 has been a busy year here at Sider so far, and our team has shipped multiple updates including those of our UI. Based on our users’ feedback, complaints and suggestions, some tweaks were made to Sider’s UI to improve the ease of use and overall experience. …

In Sider, you can specify branches to exclude from analyses in sideci.yml. Today, regular expressions are now available as the branch pattern. For example, your team has a naming convention like release-#{release_date} for release branches and you do not want to analyze these branches, you can write the following: linter: # ... branches: exclude: - /^release-.*$/ Please also see the documentation for details.

Sider allows closing each issue within a pull request to assert the issue is “wontfix” or “confirmed”. This feature is available to all users in the GitHub repository who have write permission or higher. See Permissions for details. Now, users with admin permissions for the repository can restrict closing issues only to users with admin permissions. To enable this setting, click the “Admin” tab from the Repository Settings and click the “Restrict close button”.

Today, we introduce new ways to install gems for RuboCop analysis. Currently, Sider allows you to install RuboCop plugins and configuration gems via the gems option in sideci.yml. linter: rubocop: gems: - name: "rubocop" version: "0.63.1" - name: "meowcop" version: "1.17.0" In addition to the above, Sider now supports the…

Today, we are excited to announce that public analysis pages are available to open source communities! Previously, regardless of whether your repository was public or private, users (for example, a contributor to your project) had to sign up for Sider to view analysis results. As of today, if the repository is public, anyone can view analysis results without signing in. However, you will still need to sign in if you want to post comments via Sider, close issues, and so on.

Happy New Year! I hope 2019 will bring you many joys and wonderful moment. In Japan, we celebrate New Year as one of the most important seasonal events. We will resume our regular posts from January 17th so please stay tuned! As this year’s Japanese Zodiac sign from twelve earthy branches is a boar, Sider will continue to move forward with our mission: bring Better Code Review for Better Products.

Whether you are enjoying the holiday gatherings or trying to meet your Q4 deadlines before the new year comes, we wish you a wonderful season. Our contents team will be taking a winter break for the rest of December to the 2nd week of January. Please come back for our new tech blog post on January 17th. Happy Holidays! Sider For more information about Sider, please go to our website.

We have uploaded a new customer story — scouty! Scouty is an AI career matching service which uses open source data on the internet. Scouty uses JS, Python, CSS and chose Sider to help with their code reviews. This story explains how Sider improves development efficiency for both developers and designers. It should be helpful for understanding how Sider can improve your product development process.