fix: fixed broken links (#1838)

Author: Vamshi-Microsoft

.github/workflows/broken-links-checker.yml

@@ -36,6 +36,7 @@ jobs:
           args: >
             --verbose --exclude-mail --no-progress --exclude ^https?://
             ${{ steps.changed-files.outputs.md_files }}
+          failIfEmpty: false
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
@@ -46,6 +47,7 @@ jobs:
           args: >
             --verbose --exclude-mail --no-progress --exclude ^https?://
             '**/*.md'
+          failIfEmpty: false
           output: lychee/out.md
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

code/tests/functional/tests/backend_api/README.md

@@ -13,7 +13,7 @@ existing set of tests, rather than creating a new set, as this removes the need
 starting up a new instance of the application on another port.
 
 New environment variables common to all tests can be directly added to the `config`
-dict in [app_config.py](../app_config.py), while variables only needed for one set
+dict in [app_config.py](../../app_config.py), while variables only needed for one set
 of tests can be added to the `app_config` fixture in the respective `conftest.py`
 file, e.g. [./default/conftest.py](./default/conftest.py).
 

docs/LOCAL_DEPLOYMENT.md

@@ -223,7 +223,7 @@ Execute the above [shell command](#L81) to run the function locally. You may nee
 
 ## Bicep
 
-A [Bicep file](./infra/main.bicep) is used to generate the [ARM template](./infra/main.json). You can deploy this accelerator by the following command if you do not want to use `azd`.
+A [Bicep file](../infra/main.bicep) is used to generate the [ARM template](../infra/main.json). You can deploy this accelerator by the following command if you do not want to use `azd`.
 
 ```sh
 az deployment sub create --template-file ./infra/main.bicep --subscription {your_azure_subscription_id} --location {search_location}

docs/TEAMS_LOCAL_DEPLOYMENT.md

@@ -1,4 +1,4 @@
-[Back to *Teams Extension* README](./TEAMS_EXTENSION.md)
+[Back to *Teams Extension* README](./teams_extension.md)
 
 ## Local deployment for Teams
 

docs/advanced_image_processing.md

@@ -12,7 +12,7 @@ All of this allows a user to ask questions about the meaning of images in the kn
 
 Compare the results when uploading the following image:
 
-![image](./images/architecture.png)
+![image](./images/architecture_pg.png)
 
 Without advanced image processing:
 

docs/design/adrs/template.md

@@ -1,6 +1,6 @@
 # [short title of solved problem and solution]
 
-* **Status:** [proposed | rejected | accepted | deprecated | … | superseded by [ADR-0005](0005-example.md)]
+* **Status:** [proposed | rejected | accepted | deprecated | … | <!-- superseded by [ADR-0005](0005-example.md) -->]
 * **Proposer:** [list everyone involved in the proposal]
 * **Date:** [YYYY-MM-DD when the decision was last updated]
 * **Technical Story:** [description | ticket/issue URL] <!-- optional -->
@@ -58,4 +58,4 @@ Chosen option: "[option 1]", because [justification. e.g., only option, which me
 ## Links <!-- optional -->
 
 * [Link type] [Link to ADR] <!-- example: Refined by [ADR-0005](0005-example.md) -->
-* … <!-- numbers of links can vary -->
+* … <!-- numbers of links can vary -->

docs/employee_assistance.md

@@ -52,7 +52,7 @@ Context:
 You can see the [Employee Assistant Prompt](../code/backend/batch/utilities/helpers/config/default_employee_assistant_prompt.txt) file for more details.
 
 ## Sample Employee Policy and Handbook Data
-We have added sample Employee data in the [Employee Assistant sample Docs](../data/employee_data) folder. This data can be used to test and demonstrate the Employee Assistant's capabilities.
+We have added sample Employee data in the [data](../data/) folder. This data can be used to test and demonstrate the Employee Assistant's capabilities.
 
 ## Conclusion
 This README provides an overview of the Chat With Your Data Employee Assistant prompt, instructions for updating the prompt configuration, and examples of questions and answers. Ensure you follow the guidelines for updating the prompt to maintain consistency and accuracy in responses.

docs/images/cwyd_admin_contract_unselected.png

@@ -32,7 +32,7 @@ azd up
 ```
 
 These commands will provision the necessary Azure Machine Learning resources and establish the flow in
-[../infra/prompt_flow/cwyd/](../infra/prompt_flow/cwyd/) as a managed endpoint.
+[../infra/prompt-flow/cwyd/](../infra/prompt-flow/cwyd/) as a managed endpoint.
 
 
 Upon first accessing the deployed flow in Azure Machine Learning Studio, you may encounter errors as shown below:
@@ -46,7 +46,7 @@ This is a known issue and can be resolved by initiating a compute session. Once
 Follow these steps to update the flow:
 
 1. Navigate to the flow in Azure Machine Learning Studio and make the necessary changes
-1. Download the updated flow files to the [../infra/prompt_flow/cwyd/](../infra/prompt_flow/cwyd/) directory by clicking the download button in the Files tab
+1. Download the updated flow files to the [../infra/prompt-flow/cwyd/](../infra/prompt-flow/cwyd/) directory by clicking the download button in the Files tab
 ![Download](images/prompt-flow-download.png)
 1. Replace the content of `flow.dag.template.yaml` with your new flow from the `flow.dag.yaml` file
 1. In the `flow.dag.template.yaml` file, locate the `inputs.mlindex_content` section for the `lookup` node and replace

docs/prompt_flow.md

@@ -25,15 +25,15 @@ Installing Playwright Pytest from Virtual Environment
 Run test cases
 - To run test cases from your 'tests\e2e-test' folder : "pytest --headed --html=report/report.html"
 
-Steps need to be followed to enable Access Token and Client Credentials 
+Steps need to be followed to enable Access Token and Client Credentials
 - Go to App Service from the resource group and select the Access Tokens check box in 'Manage->Authentication' tab
-![img.png](img.png)
+<!-- ![img.png](img.png) -->
 - Go to Manage->Certificates & secrets tab to generate Client Secret value
-![img_1.png](img_1.png)
+<!-- ![img_1.png](img_1.png) -->
 - Go to Overview tab to get the client id and tenant id.
 
 Create .env file in project root level with web app url and client credentials
-- create a .env file in project root level and add your user_name, pass_word, client_id,client_secret, 
+- create a .env file in project root level and add your user_name, pass_word, client_id,client_secret,
         tenant_id, web_url and admin_url for the resource group. please refer 'sample_dotenv_file.txt' file.
 
 ## Documentation