As a former program ape, I has also been “enjoying” those selfless sharing from the open source community. These open source projects on their own impact and inspiration is still very large, have thought before how to give back to the open source community, but also opened some of their own projects, participated in some open source projects, but are still only domestic projects. Not long ago, I saw Jimmy Song in the WeChat Circle of Friends to release the dynamics of the Istio official website translation team established and volunteer recruitment, without any hesitation, after work contact Jimmy applied to join the translation work, and in the following time to complete his first translation, also successfully merged into the main branch of Theo official warehouse. If you have the same idea as me, then you are welcome to join us and look forward to it.
You were born as a programmer and certainly know the importance of backup. Besides, in the context of the current environment, the political relations in the United States are still rather chaotic, and for the projects stored on Github, it is no longer a country of technological freedom. So it’s still necessary for our code to have a “double” backup, and then we’ll show you how to use Action on Github to synchronize the code above Github to the Gitee warehouse site in China.
555, today experienced a “pleasure” to install the latest program!!!
When you used GitExtensisons to push the latest written article to Github, I encountered an inexplicable error that invalidated SSH KEY authentication. Here’s how it happened: Today, when you first open Git Extensions, it’s very friendly to pop up the update prompt window, and then you click the confirmation button unconsciously. When the results are updated, an error blocking as magical as the following occurs when pushing the article to Github:
FATAL ERROR: No supported authentication methods available (server sent: publickey) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
There’s always something new on Github, and it’s not unwittingly an interesting game to play with as a personal developer’s lettercard. The effect is as follows:
It’s not cumbersome to operate, as was the case with previous pages services, just prepare a specific repository, as follows:
After some consideration or moving your personal blog from the Hexo engine to the Hugo engine, the blog theme is still NexT. In fact, I was worried about tossing up a brand new blog theme, and then I saw the “NexT”(https://github.com/xtfly/hugo-theme-next) theme shared by Lanlings on Github and quotedit directly. However, after deployment, there are areas that need to be improved, and the process of retrofitting optimization is documented here. If you also like this topic, then welcome to use, also welcome to exchange feedback.