deploy change log and announcement updates#440
Conversation
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Sanjana Podduturi <59354376+P-Sanjana@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
Deploying animata with
|
| Latest commit: |
fb1c3d1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://95d61549.animata.pages.dev |
| Branch Preview URL: | https://main.animata.pages.dev |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fb1c3d10fa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <CSPostHogProvider> | ||
| <div vaul-drawer-wrapper=""> | ||
| <div className="relative flex min-h-screen flex-col bg-background"> | ||
| <AnnouncementRibbon repeat={12} className="sticky top-0 z-60" /> |
There was a problem hiding this comment.
Adding a sticky AnnouncementRibbon above the sticky header increases the fixed top chrome to 6.25rem, but docs/blog heading anchors still rely on scroll-m-20 (5rem) in the MDX heading components. In practice, TOC/hash-link navigation on docs and blog pages now scrolls targets under the ribbon+header, so the heading appears partially hidden. Please update the anchor offset (ideally via a shared top-offset token) to match the new stacked sticky height.
Useful? React with 👍 / 👎.
2 participants
No description provided.