From 800eb5f6ccd0ba51cab8f8c03040e6256c55764c Mon Sep 17 00:00:00 2001 From: GarvitLT Date: Wed, 3 Dec 2025 14:53:27 +0530 Subject: [PATCH] Added Azure Repos in Rerun --- docs/hyperexecute-rerun-failed-tests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hyperexecute-rerun-failed-tests.md b/docs/hyperexecute-rerun-failed-tests.md index f9e9a367..18ffd627 100644 --- a/docs/hyperexecute-rerun-failed-tests.md +++ b/docs/hyperexecute-rerun-failed-tests.md @@ -46,7 +46,7 @@ To address this, HyperExecute supports Rerun Job functionality, a feature that a ## Prerequisites To rerun a job, the following requirements must be fulfilled. -- Your test suite should be available on **Git** (Github and Bitbucket are supported) and linked to a [Project](/support/docs/hyperexecute-projects). This is required because each time a job is rerun, HyperExecute needs access to your test suite. +- Your test suite should be available on **Git** (Github, Azure Repos and Bitbucket are supported) and linked to a [Project](/support/docs/hyperexecute-projects). This is required because each time a job is rerun, HyperExecute needs access to your test suite. - Make sure you are using **YAML version 0.1** with auto-split mode and discovery mode as local only. > Support for YAML version 0.2 and other modes will be added soon.