Skip to content

ci: check the README's C# blocks against the package - #18

Merged
rgfaber merged 1 commit into
mainfrom
juno/doc-snippets-v2
Oct 21, 2026
Merged

rgfaber merged 1 commit into
mainfrom
juno/doc-snippets-v2

Conversation

@rgfaber

@rgfaber rgfaber commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Purpose (usability): a reader who copies a C# block out of this package's README gets code that compiles against the package, and a block that stops compiling fails CI before it ships (macula-io/macula-codebase-checks#8).

  • ci.yml: a docs job calling macula-io/macula-ci-images/.github/workflows/doc-snippets-csharp.yml pinned by full commit SHA (d25a36c). The workflow has no paths-ignore, so a doc-only change runs it.
  • release.yml: the same check at the tag, and publish has needs: [release-guard, docs], so the package that reaches NuGet is the one the blocks were compiled against.

The check builds the package, wraps each README block in a fragment or a file, and maps every compiler error back to the doc line. Locally it reports 0 failures in 4 blocks, and it ran green on the same commit's first draft PR (#17), which this rebase replaces.

Refs macula-io/macula-codebase-checks#8

🤖 Generated with Claude Code

A reader who copies a C# block out of the README gets code that compiles against
this package, and a block that stops compiling fails CI before it ships. The job
calls the shared check pinned by full commit SHA; a doc change runs it, since
neither workflow has a paths-ignore.

The release waits on it: release.yml runs the same check at the tag and the
publish job needs it, so the package about to reach NuGet is the one the blocks
were compiled against.

Refs macula-codebase-checks#8
@rgfaber
rgfaber merged commit dac0818 into main Oct 21, 2026
6 checks passed
@rgfaber
rgfaber deleted the juno/doc-snippets-v2 branch October 21, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant