-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Update README.md, remove unused URLs #727
Conversation
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.
Wait...
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.
No need to uncomment badges, they stay there as backup.
No need to switch places badges, it's just variables and don't affect anything.
Also, readme's soon will be strongly refactored. Almost all links with docs must be targeted on site.
Rolling back unneded changes. Thank's.
@ivan-nginx |
@stevenjoezhang His certificate has expired but site is available. |
Yep, only this 2 changes enough. |
@1v9 Seems it was redirected to this: https://dnspod.qcloud.com/static/block.html?d=blog.zzbd.org |
@ivan-nginx OK, I'll revert some changes |
@stevenjoezhang also, u can do like me: create local branch and then push this your local branch to remote repo, to this repo (coz u have Admin rights, all members they have) and after that create pull-request from this branch to main master. It will be able to change branch here and see live preview before pull merged. Example: https://github.com/theme-next/hexo-theme-next/blob/security-section/docs/zh-CN/CONTRIBUTING.md |
@ivan-nginx Thanks, this is a better solution 👍 |
* Update README * Delete link * Update
Changes:
In Vi's repo there are many URLs in
README.md
, but most of them are removed now... However the link of them are keeped. This PR moves them into the<!-- -->
commentDeleted a link to an expired website
See: iissnan/hexo-theme-next@020109d#diff-4b29e98dc086ca7ee0e534c9eb921739
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?
How to use?
In NexT
_config.yml
:Does this PR introduce a breaking change?