Make CSS cleaner using tablet-mobile()#724
Merged
stevenjoezhang merged 5 commits intotheme-next:masterfrom Mar 22, 2019
GalaxyMimi:sidebar
Merged
Make CSS cleaner using tablet-mobile()#724stevenjoezhang merged 5 commits intotheme-next:masterfrom GalaxyMimi:sidebar
tablet-mobile()#724stevenjoezhang merged 5 commits intotheme-next:masterfrom
GalaxyMimi:sidebar
Conversation
1v9
approved these changes
Mar 22, 2019
mxdh
added a commit
to mxdh/hexo-theme-next
that referenced
this pull request
Mar 23, 2019
Code style update, using `tablet-mobile()` to make CSS cleaner (theme-next#724)
tablet-mobile() to make CSS cleanertablet-mobile()
tongluyang
pushed a commit
to tongluyang/hexo-theme-next
that referenced
this pull request
Nov 19, 2019
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
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue resolved: N/A
What is the new behavior?
All code is equivalent, no substantive changes
How to use?
In NexT
_config.yml:Does this PR introduce a breaking change?