-
Notifications
You must be signed in to change notification settings - Fork 115
fix(studio): items flows incorreclty on getting started screen #2542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
141e88f
to
055717d
Compare
0f04963
to
797ae34
Compare
055717d
to
b2dc724
Compare
797ae34
to
9a68743
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
Improves the Getting Started screen layout in Rivet Studio with better overflow handling and alignment fixes.
- Added
justify-center-safe
utility class infrontend/apps/studio/src/index.css
for safer content alignment - Modified container in
frontend/apps/studio/src/routes/_layout/index.tsx
to usesize-full
andoverflow-auto
for proper scrolling - Added margin spacing (
mt-4
) to title for better visual hierarchy
2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
Graphite Automations"Test" took an action on this PR • (06/04/25)1 assignee was added to this PR based on Kacper Wojciechowski's automation. |
Merge activity
|
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->
Changes