Problem description: It goes like this. I saw an article before about using hexo to build a blog. The tutorial is this. According to this step by step, there is no problem in submitting it to the github of account A.
But I wanted to build one again, and then followed this tutorial step by step, and then when I submitted the B accounthexo clean && hexo g && hexo d
, I found a fatal bug that I couldn’t solve~~As shown below
Error report content
remote: Permission to naihe138/naihe138.github.io.git denied to blueSky1115.
fatal: unable to access 'https://github.com/naihe138/naihe138.github.io.git/': The requested URL returned error: 403
FATAL Something's wrong. Maybe you can find the solution here: http://hexo.io/docs/troubleshooting.html
Error: remote: Permission to naihe138/naihe138.github.io.git denied to blueSky1115.
fatal: unable to access 'https://github.com/naihe138/naihe138.github.io.git/': The requested URL returned error: 403
at ChildProcess.<anonymous> (/Users/naihe/naihe138.github.io/node_modules/hexo-util/lib/spawn.js:37:17)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:827:16)
at Socket.<anonymous> (internal/child_process.js:319:11)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:477:12)
Please ask God to help me solve this problem. I have been troubled for a long time~~~
为情所困2017-05-02 09:42:25
Encountered an identical problem
The solution is to use ssh instead of https in the repo address deployed in hexo _config.yml
repository: git@github.com:Name/Name.github.io.git
But why is this? So strange
为情所困2017-05-02 09:42:25
The error message means: naihe138.github.io.git rejected the push request of blueSky1115.
This is because under the default settings, the gitbub page is a private project, and only the account corresponding to the page can push (that is, the account naihe138). According to your description, the setup of account A has been completed. I think the github account in your local hexo folder has been set to naihe138.
The fastest solution I can think of is to add push permissions to blueSky1115 in the naihe138.github.io.git repo.
If the above is not feasible, then you need to make some settings so that you can push to naihe138.github.io. For specific operations, please refer to this page: http://memoryboxes.github.io/….