![]() ![]() But that is my biased opinion, use whichever solution works best for you! IMHO I'd much rather track the actual source code and deploy the minimal amount of files in the public project, and having two completely unrelated branches in the same repository is kind of an overly obscure solution. You will need to commit the build site/ artifacts, or you could even use a different branch for the GitHub page altogether. make some changes to your markdown files or mkdocs.ymlĬan't I just run mkdocs build and use site/ as my GitHub page?.Make publish will handle the deploy and update your submodule version. ![]() So you can customize that as well.Īt this point you should have two GitHub repositories: Its README.md will appear on your public profile. Note that a repository named as your username is a special repository on GitHub.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |