From e50a24d12e0da05edb924fb8af4b9a14205fc28e Mon Sep 17 00:00:00 2001 From: Jatin Garg <48029724+jatgarg@users.noreply.github.com> Date: Thu, 3 Oct 2024 16:19:08 -0700 Subject: [PATCH] Update build-tools/packages/build-cli/docs/codeCoverageDetails.md Co-authored-by: Tyler Butler --- build-tools/packages/build-cli/docs/codeCoverageDetails.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-tools/packages/build-cli/docs/codeCoverageDetails.md b/build-tools/packages/build-cli/docs/codeCoverageDetails.md index 17a14023893c..16db0beee1e1 100644 --- a/build-tools/packages/build-cli/docs/codeCoverageDetails.md +++ b/build-tools/packages/build-cli/docs/codeCoverageDetails.md @@ -18,7 +18,7 @@ Code coverage data is included in the cobertura-format coverage files we collect ### Identifying the baseline build -Before running coverage comparison, a baseline build needs to be determined for the PR. This is typically based on the target branch for the PR. For example, if a pull request was targeting main, we would consider the baseline to be the latest successful build in that branch. +Before running coverage comparison, a baseline build needs to be determined for the PR. This is typically based on the target branch for the PR. For example, if a pull request was targeting `main`, we would consider the baseline to be the latest successful `main` branch build. ### Downloading artifacts from baseline build