-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
docs: answer frequently asked questions #351
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.
Some suggestions are for reference only.
BTW, I think we had better announce to users that if they use hexo-deployer-git
, then they should no longer make manual commits to the target repository other than using hexo-deployer-git
. Because the changes they make will always be overwritten by hexo-deployer-git
README.md
Outdated
@@ -113,6 +113,22 @@ Additional guides: | |||
- Create a GitHub Personal Access Token. [[Link]](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) | |||
- Add authentication token to Travis CI. [[Link]](https://docs.travis-ci.com/user/environment-variables/#defining-variables-in-repository-settings) | |||
|
|||
## Custom Domain Issue with CNAME File | |||
|
|||
If you are using a custom domain with GitHub Pages, you might have encountered an issue where your custom domain configuration gets lost after deploying updates to your site. This problem occurs due to the deletion of the `CNAME` file in the root of the deployed directory during the git commit and push process performed by the `hexo-deployer-git` plugin. |
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.
I think CNAME
file was overwritten rather than deleted
Co-authored-by: Uiolee <[email protected]>
Co-authored-by: Uiolee <[email protected]>
Thank you for your suggestion. I have added a section in the README explaining the force push behavior of this plugin. |
Issue resolved: #71
Issue resolved: #87
Issue resolved: #175
Issue resolved: hexojs/hexo#3513