-
Notifications
You must be signed in to change notification settings - Fork 6
feat: add build-test-dotnet workflow #636
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
Conversation
Add agentic workflow to clone and build .NET test projects through the AWF firewall, validating NuGet package restore and dotnet build work correctly with proxy configuration. - Create build-test-dotnet.md workflow (dotnet domain preset) - Compile and postprocess lock file - Add to postprocess-smoke-workflows.ts - Test repo: Mossaka/gh-aw-firewall-test-dotnet (hello-world + json-parse) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
💫 TO BE CONTINUED... Smoke Claude failed! Our hero faces unexpected challenges... |
|
📰 DEVELOPING STORY: Smoke Copilot reports failed. Our correspondents are investigating the incident... |
✅ Coverage Check PassedOverall Coverage
Coverage comparison generated by |
|
🌑 The shadows whisper... Smoke Codex failed. The oracle requires further meditation... |
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.
Pull request overview
Adds a new agentic “Build Test .NET” workflow to validate that cloning, NuGet restore, and building .NET projects work through the AWF firewall, and wires its generated lockfile into the smoke-workflow postprocessing script.
Changes:
- Add
.github/workflows/build-test-dotnet.mddefining the agentic .NET build/test procedure and expected PR comment output. - Add compiled workflow
.github/workflows/build-test-dotnet.lock.yml. - Register the new lockfile in
scripts/ci/postprocess-smoke-workflows.tsso it receives the standard postprocessing (local awf build, etc.).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| scripts/ci/postprocess-smoke-workflows.ts | Includes the new .NET lock workflow in the postprocessing list. |
| .github/workflows/build-test-dotnet.md | Defines the agent prompt/spec for cloning and running restore/build/run on .NET test projects. |
| .github/workflows/build-test-dotnet.lock.yml | Generated compiled workflow implementing the agentic run + safe outputs plumbing. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - `hello-world`: `cd /tmp/test-dotnet/hello-world && dotnet restore && dotnet build && dotnet run` | ||
| - `json-parse`: `cd /tmp/test-dotnet/json-parse && dotnet restore && dotnet build && dotnet run` |
Copilot
AI
Feb 10, 2026
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.
dotnet build implicitly performs a restore and dotnet run implicitly builds again. Since this workflow already runs dotnet restore explicitly (and wants to report restore/build/run separately), consider using dotnet build --no-restore and dotnet run --no-build (and/or --no-restore) to avoid duplicate restores/builds and to make the per-step status reporting unambiguous.
| - `hello-world`: `cd /tmp/test-dotnet/hello-world && dotnet restore && dotnet build && dotnet run` | |
| - `json-parse`: `cd /tmp/test-dotnet/json-parse && dotnet restore && dotnet build && dotnet run` | |
| - `hello-world`: `cd /tmp/test-dotnet/hello-world && dotnet restore && dotnet build --no-restore && dotnet run --no-build --no-restore` | |
| - `json-parse`: `cd /tmp/test-dotnet/json-parse && dotnet restore && dotnet build --no-restore && dotnet run --no-build --no-restore` |
|
🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨ |
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤 |
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 |
Deno Build Test Results
Overall: ✅ PASS All Deno tests passed successfully.
|
Node.js Build Test Results
Overall: PASS ✅ All Node.js projects built and tested successfully.
|
|
Smoke Test Results - Claude Engine Last 2 merged PRs:
✅ GitHub MCP: Retrieved PRs successfully Status: PASS
|
Build Test: Bun ✅
Overall: PASS All Bun projects built and tested successfully.
|
.NET Build Test Results
Overall: PASS ✅ All .NET projects successfully restored, built, and ran with expected output.
|
Rust Build Test Results
Overall: PASS ✅ All Rust projects built and tested successfully.
|
C++ Build Test Results
Overall: PASS All C++ projects built successfully.
|
Build Test: Java - ResultsTest Summary
Overall: FAIL Error DetailsBoth projects failed during the Maven compilation phase with the same error: Error: Root Cause: Maven unable to download dependencies from Maven Central Repository ( Full Error Message: AnalysisThis appears to be a network connectivity/firewall issue preventing Maven from accessing Maven Central. The SSL handshake is failing, suggesting either:
RecommendationVerify that the GitHub Actions runner environment has:
Test Repository:
|
Go Build Test Results
Overall: PASS ✅ All Go projects successfully downloaded dependencies and passed tests.
|
|
feat: add skip-unset mode to one-shot token library with value preview (enabled by default) | feat: add one-shot token LD_PRELOAD library for single-use token access
|
Smoke Test ResultsLast 2 Merged PRs:
Test Results:
Overall: PASS cc @Mossaka
|
Summary
build-test-dotnet.mdagentic workflow that clones and builds .NET test projects through the AWF firewalldotnet buildwork correctly with proxy configurationhello-world: minimal console app (no external deps)json-parse: console app with Newtonsoft.Json NuGet dependencybuild-test-dotnet.lock.ymlto postprocess scriptTest plan
🤖 Generated with Claude Code