Skip to content

Update WSO2 Choreo branding to Developer Platform in MFA guide - #6288

Open
UmairStn wants to merge 2 commits into
wso2:masterfrom
UmairStn:fix-mfa-choreo-branding
Open

Update WSO2 Choreo branding to Developer Platform in MFA guide#6288
UmairStn wants to merge 2 commits into
wso2:masterfrom
UmairStn:fix-mfa-choreo-branding

Conversation

@UmairStn

Copy link
Copy Markdown

Description

Replaces outdated "WSO2 Choreo" branding with "Developer Platform" across titles and content in the MFA advanced conditions guide.

Fixes wso2/product-is#28184

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

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

Next review available in: 36 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: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: af58f359-03c3-4064-92f8-283e83c46580

📥 Commits

Reviewing files that changed from the base of the PR and between 075ae22 and 0b38cda.

📒 Files selected for processing (1)
  • en/includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md
📝 Walkthrough

Walkthrough

Changes

Developer Platform MFA guide

Layer / File(s) Summary
Developer Platform API integration
en/includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md
Updates the guide’s branding, navigation, REST API example, and integration instructions for Developer Platform.
Conditional login-flow configuration
en/includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md
Updates login-flow steps, connection metadata, credential aliases, and API failure or timeout messages.
Guide behavior and completion content
en/includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md
Revises the “How it works” explanation and final image markup for the Developer Platform flow.

Suggested labels: Team/Authentication & registration

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is too sparse for the template; it lacks Purpose, Related PRs, Test environment, and Security checks sections. Add the required template sections, including purpose, related PRs, tested environments, and the three security check items.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: rebranding the MFA guide from WSO2 Choreo to Developer Platform.
Linked Issues check ✅ Passed The changes match issue #28184 by updating the MFA guide title, content, links, and screenshots to Developer Platform branding.
Out of Scope Changes check ✅ Passed The PR stays within scope; the documented edits are branding updates in the MFA guide and do not add unrelated code changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🤖 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.

Inline comments:
In
`@en/includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md`:
- Around line 139-142: Update the connection metadata placeholders in the
authentication example, including the corresponding entries around
asgardeoTokenEndpoint, to use clear, grammatically direct descriptions such as
the Developer Platform API URL, application consumer key, application consumer
secret, and tenant token endpoint. Preserve the existing metadata keys and JSON
structure.
- Around line 233-236: Update the failure-path wording in the callChoreo
authentication flow to use active, present-tense language, stating that the
script executes step 2 by default when the API call fails or times out; keep the
existing success-path behavior and hasRisk condition unchanged.
- Line 61: Update the hasRisk condition’s country-code placeholder to use clear,
grammatically correct wording, such as “<Specify a country code of your
choice>,” while preserving the existing comparison behavior.
- Around line 21-25: Correct the REST API section anchor by changing the
misspelled “Desgin” heading to “Design the REST API” and updating the
corresponding table-of-contents link target to `#design-the-rest-api`.
- Around line 56-57: Replace the Markdown link syntax in the http:Client
constructor with the literal https://api.ipgeolocation.io URL, while keeping the
existing ipGeolocation->get call and authentication flow unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 36eb5d96-44b7-438c-bc22-98138989bbe0

📥 Commits

Reviewing files that changed from the base of the PR and between 41bbf7f and 075ae22.

📒 Files selected for processing (1)
  • en/includes/guides/authentication/conditional-auth/add-authentications-based-on-api-calls.md

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update documentation to replace "WSO2 Choreo" with "Developer Platform" in MFA advanced conditions guide

1 participant