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
Everything is OK—the changes have been pushed to branch dotnet-code-edge-kind-internals-20260909222836-5dd8b328a27fec17. Please review the changes, including any protected files, before creating the pull request.
Introduces a small unexported edge-kind helper in the workflow edge runner and routes telemetry/stateful-edge setup through it. This keeps the Go internals closer to the .NET workflow model's explicit EdgeKind classification while preserving the existing public API and runtime behavior.
.NET Reference
dotnet/src/Microsoft.Agents.AI.Workflows/Edge.cs - defines explicit EdgeKind values for direct, fan-out, and fan-in workflow edges.
dotnet/src/Microsoft.Agents.AI.Workflows/EdgeData.cs - keeps edge data tied to a connection representation used by the edge kind.
Public API and Behavior
No public Go API changed. No intentional behavior change was made.
Tests
go test ./workflow/internal/execution ./workflow
Notes
Random .NET sample inspection covered workflow edge/run internals and shared agent JSON utilities. I rejected Run.cs because the corresponding Go run handle code already has distinct lifecycle responsibilities and any cleanup risked behavior churn. I rejected AgentJsonUtilities.cs because the Go JSON helper is already a narrow generic utility and changing serializer defaults would not be portability-only. Visible open PR checks did not show an open [dotnet-code] PR covering the workflow edge candidate; two lower-integrity PR records were unavailable to inspect. The required direct git fetch of microsoft/agent-framework was blocked by the environment, so the .NET files were inspected through the configured GitHub read bridge instead.
Note
GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch dotnet-code-edge-kind-internals-20260909222836-5dd8b328a27fec17 and are ready to review.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Tip
Your pull request is ready to create! 🎉 ✅
Everything is OK—the changes have been pushed to branch
dotnet-code-edge-kind-internals-20260909222836-5dd8b328a27fec17. Please review the changes, including any protected files, before creating the pull request.Create the pull request
The original pull request description is below.
Summary
Introduces a small unexported edge-kind helper in the workflow edge runner and routes telemetry/stateful-edge setup through it. This keeps the Go internals closer to the .NET workflow model's explicit EdgeKind classification while preserving the existing public API and runtime behavior.
.NET Reference
Public API and Behavior
No public Go API changed. No intentional behavior change was made.
Tests
Notes
Random .NET sample inspection covered workflow edge/run internals and shared agent JSON utilities. I rejected Run.cs because the corresponding Go run handle code already has distinct lifecycle responsibilities and any cleanup risked behavior churn. I rejected AgentJsonUtilities.cs because the Go JSON helper is already a narrow generic utility and changing serializer defaults would not be portability-only. Visible open PR checks did not show an open [dotnet-code] PR covering the workflow edge candidate; two lower-integrity PR records were unavailable to inspect. The required direct git fetch of microsoft/agent-framework was blocked by the environment, so the .NET files were inspected through the configured GitHub read bridge instead.
Note
GitHub Actions is not permitted to create or approve pull requests in this repository.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (63 of 69 lines)
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
github.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.