In Visual Designer you enable continuous integration (CI) by:
Select the Triggers tab.
Enable Continuous integration.
References:
https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-designer

To entirely remove unwanted files from a repository's history you can use either the git filter-branch command or the BFG Repo-Cleaner open source tool.
Reference:
https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository

WhiteSource is the leader in continuous open source software security and compliance management.
WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated denitive database of open source repositories.
Azure DevOps integration with WhiteSource Bolt will enable you to:
Detect and remedy vulnerable open source components.
Generate comprehensive open source inventory reports per project or build.
Enforce open source license compliance, including dependencies' licenses.
Identify outdated open source libraries with recommendations to update.
References: https://www.azuredevopslabs.com/labs/vstsextend/WhiteSource/

When a pipeline uses a remote, 3rd-party repository host such as Bitbucket Cloud, the repository is configured with webooks that notify Azure Pipelines Server or TFS when code has changed and a build should be triggered. Since on-premises installations are normally protected behind a firewall, 3rd-party webhooks are unable to reach the on-premises server. As a workaround, you can use the External Git repository type which uses polling instead of webhooks to trigger a build when code has changed.
References: https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for

See the solution below in explanation.
Explanation:
Step 1: Create a Project Wiki
* Navigate to Azure DevOps:
* Go to Azure DevOps and sign in with your credentials.
* Select Your Project:
* Choose Project1 from your list of projects.
* Create a Wiki:
* In the left-hand menu, select Wiki.
* Click on Create project wiki.
* Enter the name Wiki1 and click Create.
Step 2: Add Mermaid Syntax to Render a Diagram
* Open the Wiki Page:
* Navigate to the newly created Wiki1.
* Edit the Wiki Page:
* Click on Edit to start editing the wiki page.
* Insert Mermaid Diagram:
* Use the following Mermaid syntax to render a diagram. For example, to render a simple flowchart, you can use:
```mermaid
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;
* Save the Page:
* Click on Save to save your changes.
Step 3: Render the TCP Handshake Diagram
* Convert TCPHandshake.png to Mermaid Syntax:
* Since you have a sample diagram in C:\Resources\TCPHandshake.png, you need to convert this diagram into Mermaid syntax. Here's an example of how a TCP handshake might look in Mermaid syntax:
```mermaid
sequenceDiagram
participant Client
participant Server
Client->>Server: SYN
Server-->>Client: SYN-ACK
Client->>Server: ACK
* Add the Diagram to the Wiki:
* Replace the sample Mermaid syntax with the TCP handshake diagram syntax in the wiki page.
* Save the Page:
* Click on Save to save your changes.
By following these steps, you will have created a project wiki named Wiki1 and used Mermaid syntax to render a diagram