docs: reframe README around template usage and fix the stale Test badge#181
Merged
Merged
Conversation
> 🤖 Generated by the Daily AI Assistant
Code Coverage OverviewLanguages: C# C# / code-coverage/dotnetThe overall coverage in the branch is 100%. Coverage data for the branch is not yet available. Show a code coverage summary of the most covered files.
Code Coverage is in Public Preview. Learn more and provide us with your feedback. |
There was a problem hiding this comment.
Pull request overview
Docs-only refresh of the README to reframe it as a template-repository front door rather than a NuGet package, remove the stale Test badge that pointed to a non-existent workflow, and surface what the scaffold actually ships (house defaults, CI, release/publish flow, agent tooling).
Changes:
- Replace "install from NuGet" framing with a "Use this template" flow (gh CLI / Use-this-template button → rename
Example→dotnet build/dotnet test). - Remove the broken Test badge (pointed to a non-existent
test.yaml); keep the accurate License badge. - Add a "✨ What's included" section describing house defaults, CI model, release/publish chain, dependency tooling, and agent setup.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #169. Part of the roadmap epic #167 (direction 2 — accurate, helpful docs). Mirrors the merged go-template README enrichment so the two templates read consistently.
Problem
The README didn't read like the front door of a template repository:
dotnet add package <package-name>from NuGet, and "Usage" was genericdotnet new/dotnet slnboilerplate. This repo is a GitHub template (is_template: true) — the real entry point is Use this template, then renamingExample.…/actions/workflows/test.yaml, but there is notest.yaml(workflows areci.yaml,publish.yaml,release.yaml,sync-labels.yaml,todos.yaml), so it rendered a "not found" status.Change
gh repo create --template/ the Use this template button → renameExample→dotnet build/dotnet test).ci.yamlonly runs onpull_request/merge_group(notpush: main), so a workflow badge wouldn't render a meaningful status on the default branch, and there's no published NuGet package or .NET-template badge analogous to go-template's Go-ecosystem badges. Kept the accurate License badge. (Acceptance criterion: Test badge fixed or removed.)Nullable,ImplicitUsings,AnalysisMode=All,EnforceCodeStyleInBuild, XML docs,TreatWarningsAsErrors), the required-checks CI model + org-required reusable validation workflow, the semantic-release →v*tag →publish-dotnet-library(NuGet) flow, Dependabot/Renovate, andAGENTS.md+.claude/skills/maintain.net10.0) rather than hardcoded prose, mirroring go-template deferring the Go version togo.mod.Acceptance criteria
Validation
Docs-only; every relative link resolves against the repo tree (
Example.slnx,src/Example,tests/Example.Tests,.editorconfig, the three workflow files,AGENTS.md). All facts (house-default properties, workflow triggers, release/publish chain) verified againstsrc/Example/Example.csproj, the workflow YAML,.releaserc, and themainbranch ruleset.