Update ci-jobs.md

One of our customers shared this example and wanted to add this to the troubleshooting segment for any other customers that may experience the same issue. [ZD ticket](https://dbtcloud.zendesk.com/agent/tickets/71658)

website/docs/docs/deploy/ci-jobs.md

@@ -216,7 +216,9 @@ If you're on a Virtual Private dbt Enterprise plan using security features like
 
 When you start a CI job, the pull request status should show as `pending` while it waits for an update from dbt. Once the CI job finishes, dbt sends the status to Azure DevOps (ADO), and the status will change to either `succeeded` or `failed`. 
 
-If the status doesn't get updated after the job runs, check if there are any git branch policies in place that's blocking ADO from receiving these updates. You can find relevant information here:
+If the status doesn't get updated after the job runs, check if there are any git branch policies in place that's blocking ADO from receiving these updates. An example of a branch policy that would result in this issue is enabling "Reset conditions" under "Status checks". If you toggle on "Reset status whenever there are new changes", this will impact dbt's ability to update ADO about the status of your CI job run.
+You can find relevant information here:
+- [Azure DevOps Services Status checks](https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops&tabs=browser#status-checks)
 - [Azure DevOps Services Pull Request Stuck Waiting on Status Update](https://support.hashicorp.com/hc/en-us/articles/18670331556627-Azure-DevOps-Services-Pull-Request-Stuck-Waiting-on-Status-Update-from-Terraform-Cloud-Enterprise-Run)
 - [Pull request status](https://learn.microsoft.com/en-us/azure/devops/repos/git/pull-request-status?view=azure-devops#pull-request-status)