We’re very excited to announce that our Organization Coding Standards feature just got better! It’s now effortless and fast for admins to set up 10 tailored code pattern settings, no matter how many repositories you have.

Let’s look closer at how you can take advantage of this feature.

Organization Coding Standards explained

Coding standards are conventions and best practices for specific programming languages that you can apply to your repositories.

These settings started by being located exclusively at the repository level. Then, we introduced organization coding standards, allowing you to apply these rules seamlessly across teams or organizations. However, in the previous beta version, you could only create and edit one standard.

We now took organization coding standards to the next level, allowing you to create and configure up to 10 coding standards (yes, ten!) that can be shared between multiple repositories. This way, you can manage diverse tech stack configurations, tackle security compliance, and leverage Codacy Quality further to empower your development team.

With the current release of the organization coding standards, you can:

• Create multiple coding standards, either from scratch or from a previously set up repository. In this last scenario, Codacy Quality will help you pre-select the languages, tools, and patterns defined in the repository’s code patterns page.
• Edit the standards you previously created, in case you need to change languages, tools, patterns, and repositories that follow the coding standard. It can also be a change as simple as modifying the name of the standard. 
• Make a coding standard as default, so that new repositories in your organization can automatically follow the default coding standard without any extra configuration.
• Delete coding standards that are no longer applicable or useful for your team.

Any changes in the tools or patterns configurations at the repository level will make the repo stop following the coding standard. But we’ve got your back, and Codacy Quality will warn you and ask for your confirmation before proceeding with the change.

Ideas on how to use multiple coding standards

Do you need help with what to create in terms of coding standards? Here are some useful use cases for you, and you can even mix them up. You can have up to 10 coding standards to have fun creating your own!

For security compliance

Your organization handles sensitive data, and you have high-security standards. Your coding standard can include all the security-related patterns and those with a critical severity level.

For code style

You want to guarantee that all your teams use the same code style since it will help them better understand the source code and avoid introducing errors.

For specific teams

You might need different standards for different teams — your organization, your rules. So, you can create a standard that will only be applied to the repositories of the front-end team and another that will be applied to the back-end team.

For specific programming languages

You have several repositories in different programming languages, but you want a standard to cover all your repositories in JavaScript (or the language of your choice).

A handy tutorial just for you

To help you get started, we’re sharing a video tutorial showing how to implement organization coding standards. You can also follow the step-by-step guide on our docs page.

Let us know if you’ve any questions about this feature or would like further guidance. We’d be more than happy to help you!

We’re very excited about this new release, but your feedback is essential to us! So please give us your thoughts on how we can further improve this feature. Feel free to contact the support team in the in-app chat.

Using Codacy Quality to track your code coverage will save you time, improve the quality of your code, and give you the peace of mind that your code is up to standards. Try it out and see the difference it makes in your code review process. Start a free 14-day trial of Codacy Quality today!