Fix blog banner layout (#2300) #2383
Merged
Conversation
This file contains 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
* Fix blog banner layout * Fix banner stretching with no content
efb4f5ff-1298-471a-8973-3d47447115dc
approved these changes
Jul 7, 2022
efb4f5ff-1298-471a-8973-3d47447115dc
added
the
PR: waiting for review
efb4f5ff-1298-471a-8973-3d47447115dc
requested review from
PikachuEXE,
absidue and
ChunkyProgrammer
ChunkyProgrammer
approved these changes
Jul 7, 2022
absidue
approved these changes
Jul 7, 2022
github-actions
bot
removed
the
PR: waiting for review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix blog banner layout
Fix banner stretching with no content
Fix blog banner layout
Pull Request Type
Please select what type of pull request this is:
Related issue
#2297
Description
Fixes a layout error with the blog notification banner
Screenshots (if appropriate)
See #2300
Testing (for code that is not small enough to be easily understandable)
Yes, merged into development already
Desktop (please complete the following information):
Additional context
Created pr because creator did not create the one fore RC