Add docs to Azure Devops pr scans

[FelipePLima]

Add new doc to Azure Devops PR scans!

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds documentation for Azure DevOps PR Scans functionality and updates the existing Azure DevOps integration guide with cross-references. A new page is introduced covering PR Scan triggering mechanisms, prerequisites, enablement steps via a toggle, and behavioral details. The documentation includes a feature comparison table, troubleshooting guidance for scan failures and status/comment issues, and a support checklist. The main Azure DevOps documentation is updated with a "Related Guides" section linking to the new PR Scans and AST Orchestrator guides.

Possibly related PRs

• Add Azure Devops doc #517: Introduces the initial Azure DevOps integration documentation that this PR builds upon and cross-references.

Suggested reviewers

• eduardoconviso

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding documentation for Azure DevOps PR scans, which matches the new documentation file and related guide addition.
Description check	✅ Passed	The description is concise and directly related to the changeset, indicating the addition of new documentation for Azure DevOps PR scans.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/integrations/azure-devops-pr-scans.md (1)

127-127: 💤 Low value

Add a final newline for markdown convention compliance.

Most markdown files and linters expect a newline character at the end of the file. While this doesn't affect rendering, it's a widely adopted convention.

📝 Suggested fix

Add a blank line after line 127.

 - Approximate event timestamp
+

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/integrations/azure-devops-pr-scans.md` at line 127, The file ends
without a trailing newline; open docs/integrations/azure-devops-pr-scans.md,
confirm the last visible line reads "Approximate event timestamp" and add a
single blank newline character at EOF so the file ends with a final newline to
satisfy markdown/linter conventions.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/integrations/azure-devops-pr-scans.md`:
- Line 127: The file ends without a trailing newline; open
docs/integrations/azure-devops-pr-scans.md, confirm the last visible line reads
"Approximate event timestamp" and add a single blank newline character at EOF so
the file ends with a final newline to satisfy markdown/linter conventions.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b915bfc2-f16f-4dbb-b4fa-1a4738103c6f

📥 Commits

Reviewing files that changed from the base of the PR and between 4000a28 and d2b4135.

📒 Files selected for processing (2)

• docs/integrations/azure-devops-pr-scans.md
• docs/integrations/azure-devops.md