You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doc publishing is currently done completely manually. Ideally, once any update is done to master on any of the repos (npgsql, EF Core provider, EF6 provider) the change would automatically go live.
This would mean two things:
Continuous deployment on each of the 3 repos which detects changes on the master branch, and updates the appropriate git submodule on the doc repo. Pushing this would trigger:
Continuous deployment on https://github.com/npgsql/doc which automatically generates the site on each commit and pushes it to github (deploying live)
We should wait and see if we're transitioning from Appveyor/Travis to Azure Pipelines before attacking this.
The text was updated successfully, but these errors were encountered:
Doc publishing is currently done completely manually. Ideally, once any update is done to master on any of the repos (npgsql, EF Core provider, EF6 provider) the change would automatically go live.
This would mean two things:
We should wait and see if we're transitioning from Appveyor/Travis to Azure Pipelines before attacking this.
The text was updated successfully, but these errors were encountered: