Watch our latest Product Showcase

Group 370

Meet us at WeAreDevelopers World Congress in Berlin

Group 370

Spotlight Whitepaper by IDC on Importance of Automated Code Review Technologies

Group 370

Organization Coding Standards: Beta version is now live!

In this article:
Subscribe to our blog:

You spoke; we listened! We’re excited to announce that admins can now set organization coding standards in Codacy! 🎉 With this new feature, it will be much easier to define and manage coding patterns in multiple repositories simultaneously.

Gain time back with organization coding standards

In a nutshell, a coding standard is a way for you to set a group of tools and patterns to multiple repositories with programming languages in common.

Previously, these settings were located exclusively at the repository level. To keep adding value to our customers, we decided to move forward and took coding standards to the next level: you can now apply these rules seamlessly across teams or organizations.

You can now use the organization coding standard to ensure that all (or some, it’s your choice!) your existing repositories follow the same coding best practices, conventions, and security rules.

Codacy enables you to achieve organizational standardization across your teams as you fight technical debt, with just a few clicks. You gain back time to focus on what you do best. How awesome is that?

Create a coding standard at Codacy

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

  • Create one standard, either from scratch or from a previously setup repository. In this last scenario, Codacy will help you and pre-select the languages, tools, and patterns that were defined in the code patterns page of the repository;
  • Edit the standard you created, in case you need to change to languages, tools, patterns, and repositories that follow the coding standard.

Any change in the tools or patterns configurations at the repository level will make it stop following the standard. But worry not, Codacy will warn you and ask for your confirmation before proceeding to the change.

Ideas for standards you can create

Are you not sure what to create in terms of coding standards? Here are some use cases for you. Just keep in mind that, in the current beta version, you can only create one standard, but soon you’ll be able to have all the standards your heart desires!

For specific 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).

programming languages

For security checks

Your organization handles sensitive data, and you have high-security standards. Your coding standard can include all the tools related to security, and you select all the severity levels available: minor, medium, and critical.

security levels

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.

code style

For specific teams

You might need to have different standards for different teams — your organization, your rules. So, you can create a standard that is only going to be applied to the repositories of the front-end team (or the team(s) of your choice).

front-end teams

Among many others! Have fun creating your standard!

A handy tutorial just for you 💁‍♀️

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

If you’ve got any questions on this feature or would like some further guidance on setting it up, please let us know. We’d be more than happy to help you!

A glimpse into the (near) future

Our team is working hard so that very soon the organization coding standards will be automatically applied to new repositories. We’re also planning on making it possible to create multiple standards for your organization, among other exciting new features! 

Inteldev code standards


Coding Problems: One Less Exception
java.util.NoSuchElementException: No value found for ‘USD’ at scala.Enumeration.withName(Enumeration.scala:124)
3 popular Python style guides that will improve your coding standards
A code style guide is a set of rules, standards, or best practices that outline how your team should write, format, and organise the source code. In an...
Why use Try instead of Scala Try Catch
Scala try catch is always an option when writing Scala code for Java like exception control flows. However, you also have the option of start using the...

Automate code
reviews on your commits and pull request

Group 13