Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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. ✨ 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 |
Summary
Replaces the deprecated
pymdownx.slugs.uslugifyreference inmkdocs.ymlwith the configurablepymdownx.slugs.slugify(case: lower). Eliminates theDeprecationWarning: 'uslugify' is deprecatedwarning seen in CloudCannon and CI build logs.Why
pymdownx.slugs.uslugifywas deprecated in pymdown-extensions in favor of the configurableslugifyfactory. The two are functionally identical whencase: loweris set, so existing tab anchor URLs do not change.Behavior change
None.
uslugifywas justslugify(case='lower')under the hood, so generated slugs and anchors are identical. Existing internal/external links to tab anchors continue to resolve.Test plan
'uslugify' is deprecatedwarning