From 3db88932c6568487539e00386103a188c43a3eb3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Thu, 16 Jul 2026 16:01:55 +0100 Subject: [PATCH 1/5] fix: use semantic table backgrounds --- .../why-does-codacy-show-unexpected-coverage-changes.md | 2 +- .../roles-and-permissions-for-organizations.md | 8 ++++---- theme/stylesheets/tokens.css | 2 ++ 3 files changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md index ed3aed2865..85227800f7 100644 --- a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md +++ b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md @@ -386,7 +386,7 @@ th.border { /*Red background*/ .background-red { - background-color: #ffe6e6; + background-color: var(--docs-danger-bg); } /*Green text*/ diff --git a/docs/organizations/roles-and-permissions-for-organizations.md b/docs/organizations/roles-and-permissions-for-organizations.md index ce8d53c205..73d6736cca 100644 --- a/docs/organizations/roles-and-permissions-for-organizations.md +++ b/docs/organizations/roles-and-permissions-for-organizations.md @@ -571,7 +571,7 @@ td:not(:first-child), th:not(:first-child) { /*Background color for row containing the Codacy permission levels*/ table:not(data-exclude) tr:nth-child(1) td { - background-color: #EBF1FF; + background-color: var(--docs-bg-brand); } /*Add vertical borders and disable horizontal borders*/ @@ -585,12 +585,12 @@ td:nth-child(1) { /*Background for cells marking various operations*/ .yes { - background-color: #E6F4EA; + background-color: var(--docs-success-bg); } .no { - background-color: #FFF1EB; + background-color: var(--docs-danger-bg); } .maybe { - background-color: #F2F9FC; + background-color: var(--docs-info-bg); } diff --git a/theme/stylesheets/tokens.css b/theme/stylesheets/tokens.css index ba7e2db9f5..7191a57cfc 100644 --- a/theme/stylesheets/tokens.css +++ b/theme/stylesheets/tokens.css @@ -4,6 +4,7 @@ --docs-bg-secondary: #F9FAFB; --docs-bg-subtle: #EFF1F5; --docs-bg-brand: #E5EFFF; + --docs-info-bg: #E5EFFF; --docs-text: #171D26; --docs-text-secondary: #475776; --docs-text-tertiary: #5F7399; @@ -67,6 +68,7 @@ --docs-bg-secondary: #11151D; --docs-bg-subtle: #1D2430; --docs-bg-brand: #091E4E; + --docs-info-bg: #091E4E; --docs-text: #F9FAFB; --docs-text-secondary: #D6DBE6; --docs-text-tertiary: #96A4C0; From 88ba302afcbc876b55fb0c914be7df39cc2a5eec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Thu, 16 Jul 2026 16:07:18 +0100 Subject: [PATCH 2/5] fix: repair coverage example table rows --- .../why-does-codacy-show-unexpected-coverage-changes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md index 85227800f7..7d1ad07223 100644 --- a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md +++ b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md @@ -272,17 +272,17 @@ The table below represents two example coverage reports reflecting a pull reques 4 Yes + 5 Yes - + 6 Yes - ClassB.java From f649bc580761e329b8d4be1f1ae502b32a3a9a9a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Thu, 16 Jul 2026 16:09:25 +0100 Subject: [PATCH 3/5] fix: use semantic documentation colors --- docs/coverage-reporter/index.md | 10 +++++----- ...why-does-codacy-show-unexpected-coverage-changes.md | 6 +++--- theme/stylesheets/tokens.css | 2 ++ 3 files changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/coverage-reporter/index.md b/docs/coverage-reporter/index.md index 8bcebcfc56..b0fb368643 100644 --- a/docs/coverage-reporter/index.md +++ b/docs/coverage-reporter/index.md @@ -237,7 +237,7 @@ Follow these instructions to validate that your coverage setup is working correc If there are commits with a status different from **Processed**, please follow the troubleshooting instructions for the corresponding error status and click the button **Test integration** to display any new coverage reports uploaded to Codacy. - ### Commit not found {: id="status-commit-not-found" style="color: #EF5454;"} + ### Commit not found {: id="status-commit-not-found" style="color: var(--docs-danger);"} Codacy doesn't have information about the commit associated with the coverage data. @@ -272,7 +272,7 @@ Follow these instructions to validate that your coverage setup is working correc - ### Branch not enabled {: id="status-branch-not-enabled" style="color: #EF5454;"} + ### Branch not enabled {: id="status-branch-not-enabled" style="color: var(--docs-danger);"} The commit associated with the coverage data doesn't belong to any branch that Codacy is analyzing. @@ -307,7 +307,7 @@ Follow these instructions to validate that your coverage setup is working correc - ### Commit not analyzed {: id="status-commit-not-analyzed" style="color: #EF5454;"} + ### Commit not analyzed {: id="status-commit-not-analyzed" style="color: var(--docs-danger);"} Due to technical limitations, Codacy only reports coverage for a commit after successfully completing the static code analysis of that commit. @@ -365,7 +365,7 @@ Follow these instructions to validate that your coverage setup is working correc - ### Final report not sent {: id="status-final-report-not-sent" style="color: #EF5454;"} + ### Final report not sent {: id="status-final-report-not-sent" style="color: var(--docs-danger);"} Codacy is waiting to receive more coverage data before reporting the coverage for a commit. @@ -391,7 +391,7 @@ Follow these instructions to validate that your coverage setup is working correc - ### Pending {: id="status-pending" style="color: #2562EA;"} + ### Pending {: id="status-pending" style="color: var(--docs-info);"} Codacy is waiting to receive valid coverage data for the files in your repository. diff --git a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md index 7d1ad07223..61e07a94c5 100644 --- a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md +++ b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md @@ -377,7 +377,7 @@ The table below displays the code coverage metrics as calculated by Codacy: /*Right border*/ th.border { - border-right: 1px solid white; + border-right: 1px solid var(--docs-border); } .border { @@ -391,11 +391,11 @@ th.border { /*Green text*/ .text-green { - color: #21c178; + color: var(--docs-success); } /*Red text*/ .text-red { - color: #ef5454; + color: var(--docs-danger); } diff --git a/theme/stylesheets/tokens.css b/theme/stylesheets/tokens.css index 7191a57cfc..a0423c5902 100644 --- a/theme/stylesheets/tokens.css +++ b/theme/stylesheets/tokens.css @@ -12,6 +12,7 @@ --docs-link-hover: #0048BD; --docs-border: #DFE4EC; --docs-border-strong: #8AB7FF; + --docs-info: #005DF0; --docs-success: #339950; --docs-success-bg: #ECF9EF; --docs-warning: #BD7600; @@ -76,6 +77,7 @@ --docs-link-hover: #8AB7FF; --docs-border: #344056; --docs-border-strong: #5784FF; + --docs-info: #5784FF; --docs-success: #66CC83; --docs-success-bg: #12351C; --docs-warning: #FFC157; From f8d4228f6d2de7a8383b00a8e29bf1f81a1daeab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Thu, 16 Jul 2026 16:15:28 +0100 Subject: [PATCH 4/5] fix: correct coverage example row span --- .../why-does-codacy-show-unexpected-coverage-changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md index 61e07a94c5..bc65dac999 100644 --- a/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md +++ b/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.md @@ -260,7 +260,7 @@ The table below represents two example coverage reports reflecting a pull reques - ClassA.java + ClassA.java 2 Yes 2 From 373d1e1c43b3b7854330a1120b8df0c89fb02c82 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Thu, 16 Jul 2026 16:21:02 +0100 Subject: [PATCH 5/5] chore: group information status tokens --- theme/stylesheets/tokens.css | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/theme/stylesheets/tokens.css b/theme/stylesheets/tokens.css index a0423c5902..1c7c776bf9 100644 --- a/theme/stylesheets/tokens.css +++ b/theme/stylesheets/tokens.css @@ -4,7 +4,6 @@ --docs-bg-secondary: #F9FAFB; --docs-bg-subtle: #EFF1F5; --docs-bg-brand: #E5EFFF; - --docs-info-bg: #E5EFFF; --docs-text: #171D26; --docs-text-secondary: #475776; --docs-text-tertiary: #5F7399; @@ -13,6 +12,7 @@ --docs-border: #DFE4EC; --docs-border-strong: #8AB7FF; --docs-info: #005DF0; + --docs-info-bg: #E5EFFF; --docs-success: #339950; --docs-success-bg: #ECF9EF; --docs-warning: #BD7600; @@ -69,7 +69,6 @@ --docs-bg-secondary: #11151D; --docs-bg-subtle: #1D2430; --docs-bg-brand: #091E4E; - --docs-info-bg: #091E4E; --docs-text: #F9FAFB; --docs-text-secondary: #D6DBE6; --docs-text-tertiary: #96A4C0; @@ -78,6 +77,7 @@ --docs-border: #344056; --docs-border-strong: #5784FF; --docs-info: #5784FF; + --docs-info-bg: #091E4E; --docs-success: #66CC83; --docs-success-bg: #12351C; --docs-warning: #FFC157;