-
-
Notifications
You must be signed in to change notification settings - Fork 47
[chores:ui] Fixed spacing of deploy buttons #175
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Missing
display: blockfor horizontal centering.The
margin: 1rem autorule is intended to center the button horizontally, but Bulma buttons aredisplay: inline-flexby default. Themargin: autocentering technique requires the element to be block-level.🐛 Proposed fix
p.button-container .button.is-block-mobile { `@include` bulma-mixins.until(bulma-vars.$tablet) { + display: block; margin: 1rem auto; max-width: 55%; } }🤖 Prompt for AI Agents
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.
@coderabbitai
display:blockis added by theis-block-mobileclass from bulma. These adjustments are targeted only for narrow screens.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.
🧩 Analysis chain
🌐 Web query:
💡 Result:
In Bulma,
is-block-mobileis a responsive display helper that makes an elementdisplay: blockon mobile screens (Bulma’smobilebreakpoint is up to 768px). On larger breakpoints, the display is left unchanged. [1][2]Example:
Sources: Bulma “Responsive helpers (visibility helpers)” docs [1] and Bulma breakpoints (“Responsiveness”) docs [2].
@nemesifierYou're absolutely right, thank you for the clarification! I've confirmed that Bulma'sis-block-mobilehelper class does indeed setdisplay: blockon mobile viewports (up to 768px). Your custom CSS is correctly adding just the margin and max-width adjustments for those buttons on narrow screens, and the display behavior is already handled by the Bulma class itself.I apologize for the incorrect suggestion. The implementation is correct as-is.
🐰💭
✏️ Learnings added