BP-2395: align integrations with marketing#189
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThis updates Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/integrations/overview.mdx`:
- Around line 47-49: The ServiceNow Card's href contains a trailing space in the
string (see the Card with title "ServiceNow (SIR)" and its href attribute),
which can break the link; remove the trailing space so the href ends with the
exact URL fragment "#summary" (i.e., change
`href="https://store.servicenow.com/...#summary "` to
`href="https://store.servicenow.com/...#summary"`).
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/integrations/overview.mdx`:
- Around line 35-37: The Card component title currently reads "Palo Alto XSOAR"
but the description and href (/integrations/cortex-xsoar/configure) reference
Cortex XSOAR; update the title prop on the Card (the string passed to title in
the Card element that uses SO_Icon) to match the product name used elsewhere —
e.g., change to "Palo Alto Cortex XSOAR" or simply "Cortex XSOAR" so it is
consistent with the description and href.
🧹 Nitpick comments (1)
docs/integrations/overview.mdx (1)
73-85: Nit: Community integrations still uses<Columns>while the other sections use<CardGroup>.The supported and third-party sections were both migrated to
<CardGroup>. Was keeping<Columns cols={2}>here intentional (e.g., for visual distinction), or should it also be updated for consistency?
There was a problem hiding this comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/integrations/overview.mdx`:
- Around line 30-51: The ServiceNow Card (title "ServiceNow (SIR)") had its
trailing space in the href fixed and the Cortex card title has been corrected to
"Cortex XSOAR"; no further code changes are required—please approve and merge
the PR as-is, verifying the Cards for "AzureHound Managed Application", "Cortex
XSOAR", "Splunk", "SplunkSOAR", and "ServiceNow (SIR)" render and link correctly
in the preview.
Purpose
This pull request (PR) aligns the integrations overview page on the doc site with the integrations page on the marketing site.
See BP-2395 for details.
Staging
https://specterops-bp-2395-integrations-alignment.mintlify.app/integrations/overview
Summary by CodeRabbit