Merge pull request #426 from codacy/doc/suggest-rebase-branch

doc: Suggest rebasing branch to fix missing coverage variation
codacy · Nov 9, 2022 · 646327a · 646327a
2 parents 81482dc + eb6a1c2
commit 646327a
Showing 1 changed file with 5 additions and 2 deletions.
diff --git a/docs/index.md b/docs/index.md
@@ -214,8 +214,11 @@ Because of this, to ensure that all code coverage metrics are available on Codac
 !!! note "Example"
     The example below shows that after pushing a commit that correctly sets up coverage on the main branch:
 
-    -   Codacy will report coverage metrics for all subsequent commits and pull requests relative to the main branch
-    -   Codacy won't report coverage metrics for commits and pull requests that are relative to older branches where the coverage setup wasn't performed yet
+    -   Codacy will report coverage metrics for all subsequent commits and pull requests relative to the main branch.
+
+    -   Codacy won't report coverage metrics for commits and pull requests that are relative to older branches where the coverage setup wasn't performed yet.
+
+        To solve this issue, you can rebase the old feature branch to update the common ancestor commit to one that already has coverage data.
 
     ![Setting up coverage on the main branch](images/coverage-validate.png)