Updated Azure DevOps doc

[bharathk08]

Summary by CodeRabbit

• Documentation
  • Updated the Azure DevOps integration guide with a refreshed structure and clearer section links.
  • Rewrote setup and prerequisite steps for a smoother CI/CD onboarding flow.
  • Added more detailed pipeline creation instructions, including the updated shell script path example.
  • Expanded the run-and-results section with step-by-step guidance for checking runs and downloading reports.

[coderabbitai]

Warning

Review limit reached

@bharathk08, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3409f17f-d1a7-4ee4-9f67-3570498e6708

📥 Commits

Reviewing files that changed from the base of the PR and between 3be9da9 and c3c49ce.

📒 Files selected for processing (1)

• src/pages/docs/continuous-integration/azure-devops.md

📝 Walkthrough

Walkthrough

The Azure DevOps CI/CD integration doc was restructured: front matter and contextual links were updated for new section anchors, the Prerequisites and pipeline setup sections were rewritten, a shell script filename reference was corrected in the YAML example, and the Run/View Results section was rewritten as a numbered workflow.

Changes

Azure DevOps Integration Documentation

Layer / File(s)	Summary
Front matter and navigation src/pages/docs/continuous-integration/azure-devops.md	Updated page_id and contextual_links to match renamed section anchors.
Prerequisites and pipeline setup src/pages/docs/continuous-integration/azure-devops.md	Rewrote Prerequisites and pipeline setup content; corrected YAML displayName/inputs.filePath from ./cd-api.sh to ./cicd-api.sh.
Run pipeline and view results src/pages/docs/continuous-integration/azure-devops.md	Replaced the run/results narrative with a numbered workflow for running the pipeline, checking status, navigating to Test Plans > Runs, and downloading the JUnit XML report, plus a conversion note.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• testsigmahq/testsigma-docs#814: Both PRs update the same Azure DevOps integration doc, including the Azure Pipelines YAML snippet and related prerequisites.

Suggested reviewers: Santhosh-testsigma

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately reflects the main change: an Azure DevOps documentation update.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch DOC-2401

---

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

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

[coderabbitai]

🧹 Nitpick comments (1)

src/pages/docs/continuous-integration/azure-devops.md (1)

32-38: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use a real heading for Prerequisites.

The raw <p id="prerequisites"> anchor works, but it bypasses heading semantics and makes this section inconsistent with the rest of the page outline. A markdown heading keeps the same anchor while improving navigation/accessibility.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/docs/continuous-integration/azure-devops.md` around lines 32 - 38,
The Prerequisites section currently uses a raw paragraph anchor instead of a
real heading, which makes the page outline inconsistent. Update the
“Prerequisites” block in the docs page to use a proper markdown heading while
preserving the existing anchor behavior so navigation still works, and keep the
surrounding list content under the new heading.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/pages/docs/continuous-integration/azure-devops.md`:
- Around line 32-38: The Prerequisites section currently uses a raw paragraph
anchor instead of a real heading, which makes the page outline inconsistent.
Update the “Prerequisites” block in the docs page to use a proper markdown
heading while preserving the existing anchor behavior so navigation still works,
and keep the surrounding list content under the new heading.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6e72534e-7204-4e1a-9b22-84855c7f36a8

📥 Commits

Reviewing files that changed from the base of the PR and between 8f990b8 and 3be9da9.

📒 Files selected for processing (1)

• src/pages/docs/continuous-integration/azure-devops.md