dotnet-repo-workflow

Topics in the source

• .NET repo workflow
• When to Use
• Shell prerequisites
• Gates: run the repo's own harness
• Repo-specific knowledge
• Packages and lock files
• In-memory compilation harnesses
• Shipping

Building, gating and shipping changes in .NET (C#/F#) repositories: shell prerequisites, the repo's own gate harness, package/lock mechanics, and the in-memory compilation harness trap. | You hear / see | Do | |---|---| | "build/test this .NET repo", dotnet test / dotnet build failing | shell prerequisites → the repo's own gate harness | | adding a NuGet package, packages.lock.json diff appears | packages and lock files | | analyzer / code-fix / example-cleanliness tests fail with CS1061 | in-memory compilation harnesses | | "commit and open a PR" for a .NET change | shipping | Not for: writing style → the repo's own AGENTS.md; orchestrator maintenance → its operations skill. Non-login shells do not read /.bashrc, so dotnet can be "command not found" while the SDK is installed: Export once per session. Read command not found as a PATH gap and check /.dotnet/dotnet (or dotnet --list-sdks) before concluding the SDK is missing. Read the repo AGENTS.md / README first. Mature .NET repos route every gate through a build script, e.g. dotnet fsi build.fsx -- -p test|format|verify-docs-snippets|release; use those, not a hand-rolled subset of dotnet test, and note that PR CI often runs only

This is an excerpt. Refer to the complete source and its current requirements.