Andy on Volume Shadow Copy Service Error: Unexpected error querying for the IVssWriterCallback interface - how to fix that.Sz on ASP.NET Core C# - How to lock an async method according to custom IDs.Alexander Kriegisch on How to clear Google Chrome Redirect Cache for a single URL.Remove non-utf8 characters from string on How to strip invalid characters from an UTF-8 XML file or string in PHP. ![]() Tadorne on How to sync your MS Teams Calendar with Google Calendar. ![]() Resolving the “301 Moved Permanently” Error in Nginx – LEMP on How to clear Google Chrome Redirect Cache for a single URL.andrew on How to force Google Calendar to update a subscribed Calendar.Just remember to use the master bookmark when you need to work on your project files, and switch to the hg-pages bookmark when you feel like working on its Project Pages. You should see a couple bookmarks like those shown in the screenshots: master and gh-pages, each one corresponding to the GitHub branch with the same name: that's good, since they serve the same purpose. You can change your bookmark at any time with an hg update from the command-line or using the TortoiseHG contextual options. If you want to track your results, launch the TortoiseHG workbench and look to your local repository info: Type in (twice if needed) your GitHub credentials and you're done! Open the contextual menu by clicking the right mouse button over your project's folder and launch the Synchronize command. Now you just need to synchronize it to your local Mercurial repository on your hard-disk drive: you can do that using the same approach we wrote in our previous post. ConclusionsĪfter completing the aforementioned task of your choice you should've been able to add the gh-pages to your remote GitHub repository. The gh-pages branch will be added to your repository.įor a full reference guide on each step we suggest reading the official GitHub documentation. Preview your content using the free themes offered by GitHub and click on Publish Page when ready. ![]() The most simple way to achieve our goal is by using the Automatic Page Generator powered by GitHub. Open your project URL on GitHub and go to the Settings page: Image courtesy of GitHub.Ĭlick to the Automatic Page Generator button in the lower-right corner.Īuthor your content in the Markdown editor and click on Continue when done. Just a quick word regarding User & Organization Pages: we won't be talking about these. As a matter of fact we already did that, since they use the master branch of their own dedicated repository you can already manage sticking to what we already wrote in our previous post. This post is focused around Project Pages, which require us to create a specific gh-pages branch: let's see how to handle this.Ĭreate Project Pages using the Automatic Page Generator You can use these pages to create a website for your project: description, usage instructions, how-tos, demo, examples, documentation, APIs, and so on. In both cases you'll end up adding a new branch to your repo, namely gh-pages, where you will be able to put one or more web pages that will be openly accessible through the following URL: You can either create them manually by using the Git command-line or automatically by using the automated page generator software service powered by GitHub.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |