Improve styles of Gitalk & Gitment #568
Merged
stevenjoezhang merged 2 commits intotheme-next:masterfrom Jan 6, 2019
stevenjoezhang:swig
Merged
Improve styles of Gitalk & Gitment #568stevenjoezhang merged 2 commits intotheme-next:masterfrom stevenjoezhang:swig
stevenjoezhang merged 2 commits intotheme-next:masterfrom
stevenjoezhang:swig
Conversation
ivan-nginx
reviewed
Jan 6, 2019
| <script src="{{ gitalk_js_url }}"></script> | ||
|
|
||
| {% set gitalk_css_url = '//cdn.jsdelivr.net/npm/gitalk@1.4.0/dist/gitalk.css' %} | ||
| {% set gitalk_css_url = '//cdn.jsdelivr.net/npm/gitalk@1/dist/gitalk.css' %} |
Member
There was a problem hiding this comment.
Member
There was a problem hiding this comment.
So, if pull is ready, squash it.
ivan-nginx
approved these changes
Jan 6, 2019
ivan-nginx
pushed a commit
that referenced
this pull request
Jan 6, 2019
gitalk.css -> gitalk.min.css
anthqiu
pushed a commit
to anthqiu/hexo-theme-next
that referenced
this pull request
Aug 1, 2019
# By Mimi (4) and others # Via Ivan.Nginx * 'v6.x' of git@github.com:AntSYau/hexo-theme-next.git: add: details of configuration (theme-next#588) bugfix: make request time of leancloud saved and let concurrent requests pass (theme-next#519) Reorganize theme-next#576, using macro (theme-next#582) Edit Google Analytics reference file address (theme-next#580) Fix theme-next#573: [Muse & Mist] Footer is not at the bottom of the page (theme-next#574) Update Gitment URL to use jsDelivr CDN (theme-next#572) Fix theme-next#569 Valine Comment Count (theme-next#570) Improve styles of Gitalk & Gitment (theme-next#568) Optimize the loading of comment systems (theme-next#566) # Conflicts: # .github/PULL_REQUEST_TEMPLATE.md # _config.yml # layout/_macro/post.swig # layout/_partials/comments.swig # layout/_partials/github-banner.swig # layout/_scripts/schemes/muse.swig # layout/_third-party/analytics/google-analytics.swig # layout/_third-party/comments/disqus.swig # layout/_third-party/comments/gitalk.swig # layout/_third-party/comments/gitment.swig # layout/_third-party/comments/index.swig # layout/_third-party/comments/valine.swig # layout/_third-party/copy-code.swig # source/css/_common/components/header/github-banner.styl # source/css/_common/components/pages/schedule.styl # source/css/_common/components/post/post-reward.styl # source/css/_common/components/sidebar/sidebar.styl # source/css/_common/components/tags/note-modern.styl # source/css/_common/scaffolding/tables.styl Signed-off-by: Anthony Yau <antsyau@outlook.com>
tongluyang
pushed a commit
to tongluyang/hexo-theme-next
that referenced
this pull request
Nov 19, 2019
gitalk.css -> gitalk.min.css
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
2 participants
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
Gitalk, with scheme Gemini:
Gitment:
What is the new behavior?
Description about this pull, in several words...
Gitalk, with scheme Gemini:
Gitment:
How to use?
In NexT
_config.yml:Does this PR introduce a breaking change?