From 7036335c91ae1c5e339220a708579929e48a37a4 Mon Sep 17 00:00:00 2001 From: nicklem Date: Fri, 17 Nov 2023 14:18:26 +0100 Subject: [PATCH] feat: Add link to Managing branches --- .../integrating-codacy-with-visual-studio-code.md | 2 ++ 1 file changed, 2 insertions(+) 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 dc7de71a72..445574f8b2 100644 --- a/docs/getting-started/integrating-codacy-with-visual-studio-code.md +++ b/docs/getting-started/integrating-codacy-with-visual-studio-code.md @@ -66,6 +66,8 @@ The **Open Pull Requests** tab lists all open pull requests for the repository, If you switch to an analyzed branch that doesn't have an open pull request, such as the `main` or `master` branch, the **Analyzed Branch** tab appears and shows an overview of the Quality issues found in the branch, grouped by recently added, introduced by the current user, issue category, and issue severity. +See [how to manage the analysis of your repository's branches](../repositories-configure/managing-branches.md). + ## Installing the Codacy VS Code extension 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.