-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Provide workflow to automatically port API docs to dotnet-api-docs #41419
Comments
Tagging subscribers to this area: @ViktorHofer |
Cc: @carlossanlop |
Marking as 6.0.0 |
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsDuring each release cycle we add new APIs and documentation for them. Currently, the process of moving docs over from the triple-slash comments in dotnet/runtime to the API docs on https://docs.dot.net has a number of manual steps. I propose that we add a GitHub Action (preferable) or manually-triggered Azure DevOps Pipeline to auto-port the doc comments per-assembly to PRs opened against the dotnet/dotnet-api-docs repository.
|
Duplicate of #44969 |
During each release cycle we add new APIs and documentation for them. Currently, the process of moving docs over from the triple-slash comments in dotnet/runtime to the API docs on https://docs.dot.net has a number of manual steps.
I propose that we add a GitHub Action (preferable) or manually-triggered Azure DevOps Pipeline to auto-port the doc comments per-assembly to PRs opened against the dotnet/dotnet-api-docs repository.
The text was updated successfully, but these errors were encountered: