-
Notifications
You must be signed in to change notification settings - Fork 91
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
gitment迁移gitalk #82
Comments
我配置了,在本地 sudo hexo server -p 4001 能否看到?
|
你说的原来的本地仓库是我修改之前的版本吗? 这些设置在我修改后的版本才能用 |
谢谢~,那直接重新改下了,我的本地代码仓库是两年前的那干脆把你的分支合并到主分支吧。 @fnsflm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1. 前言
最近试图解决gitment报错:
object ProgressEvent
, 找到一个能用的gitment issue #175, 结果又冒出来Bad credentials
. 重新设置oauth app之类的方法也试过, 没有找到好的解决手段. 再加上考虑gitment已经是四年没维护的项目了, 所以决定还是使用gitalk.2. 展示
调了一下样式, 大概长这样, 比原来的差不少, 但总比用不了强
测试页面: http://testpage.fnsflm.xyz
个人博客: https://fnsflm.xyz
3. 使用
pull 修改后的项目: https://github.com/fnsflm/hexo-theme-gal
_config.yml
中填上原来gitment需要填的, 并将change_to_gitalk
改为true即可. 并没有删掉原来的gitment, 仍然可以选择使用.source/css/_gitalk.scss
用来改变评论区的样式source/js/comment/gitalk.js
加载gitalk4. 迁移
在原来所有的issue上都加上
Gitalk
的标签:5. 最后
layout/layout.ejs
中<script src="https://myau.moe/js/comment/gitment.browser.js"></script>
)6. bug
**[solved]**Error: Request failed with status code 403
详细讨论: gitalk/gitalk#429
The text was updated successfully, but these errors were encountered: