feat: use docfx generate docs site automatically#64
feat: use docfx generate docs site automatically#64SteveSuv wants to merge 0 commit intoDaveGreen-Games:mainfrom SteveSuv:main
Conversation
|
Thank you very much for this :) I always wanted to do this but never found the time ^^ |
|
Should I set the GitHub Pages Build and Deployment Source to |
|
use |
|
I can only run it successfully after I have merged the PR. Just out of curiosity would either be possible:
If yes would there be major disadvantages? I am just asking because it adds a lot of files to the repository, which is not a problem if this is the best way to do it, but if there is a way to keep them separate, I would prefer it. |
|
yeah, I also suggest split "metadata": [
{
"src": [
{
"src": "../../ShapeEngine", // here it is
"files": ["**/*.csproj"],
"exclude": ["**/Examples/**"]
}
],
"dest": "api"
}
],but don't worry, it's not a big probleam. |
|
I have created a new ShapeEngineDocs public repository within the DaveGreenGames organization and I invited you as a collaborator. |
|
I have closed this pr. |
what's changed:
docfxto generate api docs site automaticallypreview:
deploy:
I don't have permission do this step, so need repo author to deploy.
or you can split
Sitedir to a new repo then deploy.here's some guide to follow:
and when you finished deploy to github pages, you can put site url to repo's about.
has a api docs site will attract more fans :)