- Adding your first repository + Adding your organization to Codacy
{% else %} - - Adding your first repository + + Adding your organization to Codacy {% endif %}+ Configuring your organization +
+ {% else %} + + Configuring your organization + + {% endif %} +Configuring your repository
@@ -23,8 +34,8 @@ {% endif %}Integrating Codacy with your Git workflow
diff --git a/docs/getting-started/codacy-quickstart.md b/docs/getting-started/codacy-quickstart.md index f8fd14bc58..05b01a4c19 100644 --- a/docs/getting-started/codacy-quickstart.md +++ b/docs/getting-started/codacy-quickstart.md @@ -18,7 +18,7 @@ By integrating with your Git provider, Codacy keeps track of your team’s work, - **Duplication**: the amount of duplicated portions of code - **Coverage**: the percentage of lines of code covered by automated tests -## Adding your first repository +## Adding your organization to Codacy {% include-markdown "../assets/includes/nav-multistep-quickstart.md" %} @@ -26,7 +26,6 @@ To get started, head to [codacy.com](https://www. 1. [Signing up](#signing-up) 1. [Choosing an organization](#choosing-organization) -1. [Adding repositories](#adding-repositories) ## 1. Signing up {: id="signing-up"} @@ -38,28 +37,13 @@ Codacy will request access to your Git provider during the authorization flow. [ Now, you'll need to add or join the organizations that contain your repositories. The organization with the same name as your Git provider username contains your personal repositories. Read more about [organizations on Codacy](../organizations/what-are-organizations.md). -To start adding your repositories, select one of the organizations. +To proceed, select one of the organizations. !!! note If you can't see the organization you're looking for, [follow these troubleshooting instructions](../faq/troubleshooting/why-cant-i-see-my-organization.md).  -## 3. Adding repositories {: id="adding-repositories"} - -Next, add the repositories that you wish to analyze. Codacy begins an initial analysis as soon as you add a repository and sets everything up to ensure your next commits on that repository are analyzed. - -!!! note - You can only add repositories on Codacy if you have the [necessary permissions on your Git provider](../organizations/roles-and-permissions-for-organizations.md). - - - -Click the repository name to navigate to the repository dashboard and see the [code quality overview of your repository](../repositories/repository-dashboard.md) as soon as the initial analysis is complete: - - - -**Congratulations, your new repository is ready!** To explore the initial analysis results, [check the **Issues** page](../repositories/issues.md). - ## Next steps -The first analysis is based on default tool and pattern configurations. It's now important that you configure your repository to integrate code analysis seamlessly into your existing pipeline. See how to [configure your repository to match the use cases of your team](configuring-your-repository.md). +Before adding your repositories to Codacy, it's important that you [configure your organization](./configuring-your-organization.md) to align with your corporate policies and ensure consistent code quality across your repositories. diff --git a/docs/getting-started/configuring-your-organization.md b/docs/getting-started/configuring-your-organization.md new file mode 100644 index 0000000000..6d825711f3 --- /dev/null +++ b/docs/getting-started/configuring-your-organization.md @@ -0,0 +1,68 @@ +--- +description: Configure your Codacy organization to align with your corporate policies and ensure consistent code quality across your repositories. +nav_step: 1 +--- + +# Configuring your organization + +{% include-markdown "../assets/includes/nav-multistep-quickstart.md" %} + +Once you've added your organization to Codacy, it's important that you align it with your corporate policies and configure it to match the coding conventions and best practices that your team may already be following or that you want to promote. It's also critical to review the configurations to avoid reporting false positives or any other issues that don't bring value to your team, which can introduce unwanted delays to the development process. + +To configure your organization, follow these steps: + +1. [Configuring repository management permissions](#repository-permissions) +1. [Assigning organization manager role](#org-manager) +1. [Defining gate policies](#gate-policies) +1. [Defining coding standards](#coding-standards) +1. [Configuring default Git provider integration settings](#git-provider-settings) +1. [Adding repositories](#adding-repositories) + +## 1. Configuring repository management permissions {: id="repository-permissions"} + +[Define the Codacy roles](../organizations/roles-and-permissions-for-organizations.md#change-analysis-configuration) that can configure patterns, analyzed languages and branches, ignore issues and files, and reanalyze branches and pull requests. + + + +## 2. Assigning the organization manager role {: id="org-manager"} + +[Assign the organization manager role](../organizations/roles-and-permissions-for-organizations.md#managing-the-organization-manager-role) to members of your organization to grant them additional permissions without changing their permissions on the Git provider. For example, they will be able to manage your organization policies and integrations. + + + +## 3. Defining gate policies {: id="gate-policies"} + +[Define gate policies](../organizations/using-gate-policies.md) to ensure that Codacy uses the same quality gates across your organization repositories. + + + +## 4. Defining coding standards {: id="coding-standards"} + +[Define coding standards](../organizations/using-coding-standards.md) to ensure that multiple repositories consistently follow the same global tool and code pattern configurations. + + + +## 5. Configuring default Git provider integration settings {: id="git-provider-settings"} + +[Configure the default settings that Codacy uses to integrate with your Git provider](../organizations/integrations/default-git-provider-integration-settings.md) when you add a new repository to Codacy. This enables you to apply the same settings across your organization repositories. + + + +## 6. Adding repositories {: id="adding-repositories"} + +Next, add the repositories that you wish to analyze. Codacy begins an initial analysis as soon as you add a repository and sets everything up to ensure your next commits on that repository are analyzed. + +!!! note + You can only add repositories on Codacy if you have the [necessary permissions on your Git provider](../organizations/roles-and-permissions-for-organizations.md). + + + +Click the repository name to navigate to the repository dashboard and see the [code quality overview of your repository](../repositories/repository-dashboard.md) as soon as the initial analysis is complete: + + + +To explore the initial analysis results, [check the **Issues** page](../repositories/issues.md). + +## Next steps {: id="next-steps"} + +The first analysis is based on the organization policies and standards that you previously defined, or Codacy defaults if you haven't defined your own policies. This ensures consistent code quality across your repositories. It's now important that you [configure specific rules for each repository](configuring-your-repository.md) to integrate code analysis seamlessly into your existing pipeline. diff --git a/docs/getting-started/configuring-your-repository.md b/docs/getting-started/configuring-your-repository.md index 2d199ac1e0..ebeb6a48be 100644 --- a/docs/getting-started/configuring-your-repository.md +++ b/docs/getting-started/configuring-your-repository.md @@ -1,20 +1,20 @@ --- description: Configure Codacy to match the coding conventions and best practices that your team may already be following or that you want to promote. -nav_step: 1 +nav_step: 2 --- # Configuring your repository {% include-markdown "../assets/includes/nav-multistep-quickstart.md" %} -Once you've added your first repository, it's important that you configure Codacy's analysis tools to match the use cases of your team, such as configuring any coding conventions and best practices that your team may already be following or that you want to promote. It's also critical to review the configurations to avoid reporting false positives or any other issues that don't bring value to your team, which can introduce unwanted delays to the development process. +When adding your repositories to Codacy, the first analysis is based on the organization policies and standards. It's now important that you adjust for each repository any specific configuration where the organization settings don't apply. -You can optionally add coverage reports to detail how much of your code is covered by tests and unify your quality and coverage pipelines. You can generate coverage reports and upload them to Codacy using a range of options, such as CI/CD integration, CLI, Docker, GitHub action, and more. +You can optionally add coverage reports to detail how much of your repository code is covered by tests and unify your quality and coverage pipelines. You can generate coverage reports and upload them to Codacy using a range of options, such as CI/CD integration, CLI, Docker, GitHub action, and more. To configure your repository, follow these steps: 1. [Ignoring files](#ignoring-files) -1. [Configuring code patterns](#configuring-code-patterns) +1. [Adjusting code pattern configuration](#configuring-code-patterns) 1. [Adding coverage reports](#adding-coverage) (optional) ## 1. Ignoring files {: id="ignoring-files"} @@ -23,9 +23,9 @@ To configure your repository, follow these steps:  -## 2. Configuring code patterns {: id="configuring-code-patterns"} +## 2. Adjusting code pattern configuration {: id="configuring-code-patterns"} -[Configure the tools and code patterns](../repositories-configure/configuring-code-patterns.md) that Codacy uses to analyze your repository. If security is important for your team, review the [security and risk management dashboard](../organizations/managing-security-and-risk.md) to ensure that your configuration detects potential security issues. +[Adjust the tools and code patterns](../repositories-configure/configuring-code-patterns.md) that Codacy uses to analyze your repository. If security is important for your team, review the [security and risk management dashboard](../organizations/managing-security-and-risk.md) to ensure that your configuration detects potential security issues. !!! tip To ensure that multiple repositories consistently follow the same global tool and code pattern configurations, [use an organization coding standard](../organizations/using-coding-standards.md). diff --git a/docs/getting-started/integrating-codacy-with-intellij-ides.md b/docs/getting-started/integrating-codacy-with-intellij-ides.md index 8ecbe18c82..d288b2ef8c 100644 --- a/docs/getting-started/integrating-codacy-with-intellij-ides.md +++ b/docs/getting-started/integrating-codacy-with-intellij-ides.md @@ -31,7 +31,7 @@ In the main view, you can find the following information: 1. Make sure that the repository you’re working on is analyzed by Codacy and that you have a [repository read](../organizations/roles-and-permissions-for-organizations.md) role or higher. !!! tip - If this is your first time using Codacy, see [how to add and analyze your first repository](./codacy-quickstart.md#adding-your-first-repository). + If this is your first time using Codacy, see [how to get started](./codacy-quickstart.md#adding-your-organization-to-codacy). 1. Install the plugin from the [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/23924-codacy) or through the [plugin settings panel](https://www.jetbrains.com/help/idea/managing-plugins.html) in your IntelliJ IDE. diff --git a/docs/getting-started/integrating-codacy-with-visual-studio-code.md b/docs/getting-started/integrating-codacy-with-visual-studio-code.md index 339c659c73..a2fd8e428e 100644 --- a/docs/getting-started/integrating-codacy-with-visual-studio-code.md +++ b/docs/getting-started/integrating-codacy-with-visual-studio-code.md @@ -73,7 +73,7 @@ See [how to manage the analysis of your repository's branches](../repositories-c 1. Make sure that the repository you’re working on is analyzed by Codacy and that you have a [repository read](../organizations/roles-and-permissions-for-organizations.md) role or higher. !!! tip - If this is your first time using Codacy, see [how to add and analyze your first repository](./codacy-quickstart.md#adding-your-first-repository). + If this is your first time using Codacy, see [how to get started](./codacy-quickstart.md#adding-your-organization-to-codacy). 1. Install the extension from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=codacy-app.codacy) or through the [Extensions view in VS Code](https://code.visualstudio.com/docs/editor/extension-marketplace#_browse-for-extensions). diff --git a/docs/getting-started/integrating-codacy-with-your-git-workflow.md b/docs/getting-started/integrating-codacy-with-your-git-workflow.md index 4dab9165c8..82ca6cef59 100644 --- a/docs/getting-started/integrating-codacy-with-your-git-workflow.md +++ b/docs/getting-started/integrating-codacy-with-your-git-workflow.md @@ -1,6 +1,6 @@ --- description: Integrate Codacy with your Git workflow to display analysis results and code coverage as status checks on your pull requests and optionally block merging pull requests. -nav_step: 2 +nav_step: 3 --- # Integrating Codacy with your Git workflow diff --git a/docs/release-notes/cloud/cloud-2023-06.md b/docs/release-notes/cloud/cloud-2023-06.md index b4bbcaaf86..de58e01786 100644 --- a/docs/release-notes/cloud/cloud-2023-06.md +++ b/docs/release-notes/cloud/cloud-2023-06.md @@ -44,7 +44,7 @@ These release notes are for the Codacy Cloud updates during June 2023. - [eslint-plugin-sort-destructure-keys](https://www.npmjs.com/package/eslint-plugin-sort-destructure-keys) (TS-448) - Improved the performance of the tool Stylelint by reviewing and refactoring the tool configurations and supported packages. (TS-438) - Updated and refactored the tool Ameba. [Thanks to Sija for the contribution!](https://github.com/codacy/codacy-ameba/pull/25) (TS-417) -- There's now an onboarding tutorial to guide you through the steps of [adding and setting up your first repository](../../getting-started/codacy-quickstart.md#adding-your-first-repository). (DOCS-468) +- There's now an onboarding tutorial to guide you through the steps of [adding and setting up your first repository](../../getting-started/codacy-quickstart.md#adding-your-organization-to-codacy). (DOCS-468) ## Bug fixes diff --git a/mkdocs.yml b/mkdocs.yml index 1898188703..1fd7e39ff8 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -553,6 +553,7 @@ nav: - Documentation home: "index.md" - Getting started: - getting-started/codacy-quickstart.md + - getting-started/configuring-your-organization.md - getting-started/configuring-your-repository.md - getting-started/integrating-codacy-with-your-git-workflow.md - Integrating Codacy with your IDE: