You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/organizations/using-coding-standards.md
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,11 +165,30 @@ Tools and patterns enabled by a coding standard are enforced and cannot be disab
165
165
166
166
## Using multiple coding standards {: id="using-multiple"}
167
167
168
-
When Codacy analyzes your code using multiple coding standards, it merges the tools and patterns from each standard. Enabled tools and patterns in any applied standard will be enforced.
168
+
When Codacy analyzes your code using multiple coding standards, it merges the tools and patterns from each standard.
169
+
170
+
A common strategy is to start with a baseline standard containing fundamental rules that apply across all repositories, then layer additional standards based on specific needs. You can organize these additional standards by:
171
+
172
+
-**Topics:** for example, security, performance, or maintainability
173
+
-**Architecture:** for example, backend or frontend
174
+
-**Languages or frameworks:** for example, React, Java or Python
175
+
-**Teams or tribes:** Allow different teams or tribes to maintain their own standards while inheriting organization-wide rules
You can apply up to 10 coding standards to your organization. Standards can overlap, meaning a single repository can follow multiple standards simultaneously.
169
181
170
182
!!! important
171
183
If the same pattern appears in multiple standards, the version from the most recently created and applied standard (with its parameters) takes precedence.
Consider these points when implementing coding standards:
187
+
188
+
-**Keep maintenance simple:** Minimize overlap between standards and establish clear ownership to reduce maintenance complexity
189
+
-**Manage access:** Assign organization managers or Git provider admin roles to users who should manage (create, edit and delete) organization-level standards (learn more in [Roles and Permissions](./roles-and-permissions-for-organizations.md/#managing-the-organization-manager-role))
190
+
-**Be mindful of repository customization:** Individual repositories can have their own specific overrides through additional code patterns, custom tool configurations, or local configuration files
191
+
173
192
## See also
174
193
175
194
-[Configuring code patterns on each repository](../repositories-configure/configuring-code-patterns.md)
0 commit comments