Validate DocFX API output in C# workflow - #133
Conversation
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #36
- Update TargetFramework from netstandard2.0 to net8 to match project files - Replace $REPOSITORY_NAME template variable with 'Interfaces' - Configure proper file inclusion for README.md from parent directory - Add DocFX configuration files (docfx.json, filter.yml, toc.yml) Fixes #36 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
We need to resolve conflicts, and double check we fix all CI/CD warnings, false positives, false negatives and errors. |
|
🤖 AI Work Session Started Starting automated work session at 2026-09-24T20:08:05.807Z The PR has been converted to draft mode while work is in progress. This comment marks the beginning of an AI work session. Please wait for the session to finish, and provide your feedback. Runtime: solve |
|
CI review found two release failures that require repository/workflow maintainer action:
PR #133 now resolves its merge conflict and validates complete DocFX output. Its pull-request checks do not publish packages. |
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
📊 Context and tokens usage:
Total: (122.1K + 4.1M cached) input tokens, 19.8K output tokens, $2.437831 cost 🤖 Models used:
📎 Log file uploaded as Gist (2815KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
🎉 Auto-mergedThis pull request has been automatically merged by hive-mind.
Auto-merged by hive-mind with --auto-merge flag |
Summary
mainbranch and resolve the DocFX configuration conflicts using its project-based metadata and current table of contents.--warningsAsErrors) and verify the generated home page, namespace page, README-linked interface page, and cross-reference map before upload and after artifact download.Reproduction and regression coverage
Before this change, the workflow accepted a documentation artifact if
_site/index.htmlexisted, even when the API pages were missing. The newvalidate-csharp-docs.test.mjschecks a complete site and separately removes each required file to verify that validation fails. The workflow policy test checks that both the build and publication jobs invoke the validator and that DocFX warnings remain errors.Verification
node --test .github/scripts/*.test.mjs— 37 passed.DOTNET_ROLL_FORWARD=Major .github/scripts/validate-csharp-package.sh— 2 C# tests passed, strict build with 0 warnings and 0 errors. The local machine has .NET 10 only; CI installs .NET 8.docfx docfx.json --warningsAsErrors— 0 warnings, 0 errors; generated output passed the new validator.actionlint,bash -n .github/scripts/*.sh, andgit diff --check origin/main...HEAD— passed.CI review
The latest
mainC# run 35691769893 built DocFX with 0 warnings and 0 errors. Its release job failed because NuGet.org returned HTTP 403 for the repositoryNUGET_TOKEN; a maintainer must rotate or correct that secret. The PR workflow does not publish packages. An older C++ release run 35648595098 failed while installing the unavailable Ubuntunugetpackage in the separatelinksplatform/Workflowsreusable workflow.Fixes #36