Skip to content

Commit f8beae2

Browse files
KadritaElazarK
andauthored
Update articles/defender-for-cloud/devops-faq.md
Co-authored-by: Elazar Krieger <[email protected]>
1 parent 1d57871 commit f8beae2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/defender-for-cloud/devops-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Currently, OSS vulnerabilities, IaC scanning vulnerabilities, and Total code sca
5858

5959
Azure DevOps repositories only have the total exposed secrets available and will show `N/A` for all other fields. You can learn more about how to [Review your findings](defender-for-devops-introduction.md).
6060

61-
### Why is my Azure DevOps repository not refreshing to healthy?
61+
### Why is my Azure DevOps repository not refreshing to healthy?
6262

6363
For a previously unhealthy scan result to be healthy again, updated healthy scan results need to be from the same build definition as the one that generated the findings in the first place. A common scenario where this issue occurs is when testing with different pipelines. For results to refresh appropriately, scan results need to be for the same pipeline(s) and branch(es).
6464

0 commit comments

Comments
 (0)