-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀📄 Adds Build & Deployment of Documentation #30
Merged
FGS-BMarkham
merged 5 commits into
foxguardsolutions:master
from
brucificus:generate-docs
Dec 9, 2019
Merged
🚀📄 Adds Build & Deployment of Documentation #30
FGS-BMarkham
merged 5 commits into
foxguardsolutions:master
from
brucificus:generate-docs
Dec 9, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brucificus
force-pushed
the
generate-docs
branch
from
December 9, 2019 16:08
1eb6e0a
to
026915a
Compare
FGS-BMarkham
force-pushed
the
generate-docs
branch
from
December 9, 2019 18:19
026915a
to
3b4329f
Compare
fgsahoward
previously approved these changes
Dec 9, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Too early with that squirrel :/, :gopher: |
This adds a project that serves as a surrogate host for the `DocFx` documentation builder. The project is purposefully not added to the `sln`, as it is not a requirement of `DocFx` to do so and adding it would slow development builds. For more information, see: https://dotnet.github.io/docfx/tutorial/docfx_getting_started.html#3-use-docfx-integrated-with-visual-studio
Most of this is auto-generated by DocFx. It was only necessary to tweak the input paths and patterns in order to get a basic documentation build working.
This will help make sure we don't suffer a regression in our documentation builds.
This adds a workflow that builds & deploys our API documentation to the `gh-pages` branch, triggered by every change to the `master` branch.
brucificus
force-pushed
the
generate-docs
branch
from
December 9, 2019 19:57
3b4329f
to
5969f2e
Compare
fgsahoward
approved these changes
Dec 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the generation of documentation using DocFx & the automatic deployment of the output using a GitHub action.
This helps make sure our APIs have publicly-readable (and linkable!) documentation, while also giving us a way to extend it with Markdown if we'd like.