Repository navigation
Conversation
`[All other integrations here](qonversion.io/integrations)` has no scheme, so GitHub renders it as a repository-relative path and it 404s where the README is actually read. `https://documentation.qonversion.io/discuss-new` is left over from readme.io and 404s too — it sits in "Have a question?", which is exactly where a reader goes when something did not work. It now points at the contact form on the site, next to the existing issues link. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: qonversion/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe README updates three lines. They qualify the integrations URL, correct “paywals” to “paywalls,” and replace the discussion link with the contact form link. ChangesREADME Documentation Updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to The README links and wording are corrected without changing product behavior. This change is ready to merge. 🚥 Pre-merge checks | ✅ 8✅ Passed checks (8 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Two broken links, both from the shared README template.
[All other integrations here](qonversion.io/integrations)has no scheme. GitHub renders it as a repository-relative path, so on the rendered README it resolves togithub.com/qonversion/flutter-sdk/blob/main/qonversion.io/integrationsand 404s. Nowhttps://qonversion.io/integrations(200).https://documentation.qonversion.io/discuss-newin Have a question? is left over from readme.io and returns 404 — it is not among the redirects the docs site keeps. That is the link a reader follows when something did not work. It now points athttps://qonversion.io/contact-us(200), next to the existing GitHub issues link. The same target is used in the other SDK READMEs so the support channel is one and the same everywhere.Typo. «paywals» → «paywalls» in the A/B test bullet (it is copied across the READMEs).
Scope is deliberately narrow: links, licence, install, typo. Positioning, the opening paragraph, the bullets, the banner images and the version badge are untouched — those belong to the README template being rewritten separately.
Opened from a fork, so the review request could not be set from here — @SpertsyanKM, this one is for you.
🤖 Generated with Claude Code