Skip to content

Fix: Add reference to VS Code policy development tutorial [master]#11672

Open
wso2-engineering-bot wants to merge 1 commit into
masterfrom
fixing-issue-11204-master-1784632366
Open

Fix: Add reference to VS Code policy development tutorial [master]#11672
wso2-engineering-bot wants to merge 1 commit into
masterfrom
fixing-issue-11204-master-1784632366

Conversation

@wso2-engineering-bot

Copy link
Copy Markdown
Contributor

This PR was automatically generated by Claude AI.

  • Issue: Missing documentation for developing and testing custom policies in APIM 4.6 through VS code extension #11204
  • Type: Suggestions
  • Summary: Added a prominent tip box in the "Create a Policy" documentation page that directs users to the comprehensive "Develop and Test Policies" tutorial. This improves discoverability of the VS Code extension workflow for developing and testing custom policies locally before uploading to API Manager. The tutorial already existed but was not referenced from the policy creation page, making it difficult for users to discover.
  • Style Scope Verification: Microsoft Style Guidelines have been applied ONLY to newly added content without modifying existing content style.
  • Build Verification: Documentation built successfully with no errors.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@wso2-engineering-bot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4272c485-1340-447b-9c16-e56db30b0ba8

📥 Commits

Reviewing files that changed from the base of the PR and between 4b4d7e3 and ac6669c.

📒 Files selected for processing (1)
  • en/docs/api-design-manage/design/api-policies/create-policy.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fixing-issue-11204-master-1784632366

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant