I think it will be easier to manage automated updates to the docs by committing them on the gh-pages branch; it will give us a place to commit changes coming from Azure Pipelines without dirtying up the commit history on actual active branches.
This is done. There is now an Azure Pipeline build that will tag the sources, create the nuget package, push the documentation, and then publish the Nuget.org package.
I think it will be easier to manage automated updates to the docs by committing them on the
gh-pages
branch; it will give us a place to commit changes coming from Azure Pipelines without dirtying up the commit history on actual active branches.