Skip to content

build: add solution foundation, quality checks and CI - #1

Merged
net0well merged 4 commits into
mainfrom
build/solution-foundation
Oct 21, 2026
Merged

net0well merged 4 commits into
mainfrom
build/solution-foundation

Conversation

@net0well

Copy link
Copy Markdown
Contributor

What changed

  • Solution: .NET 10 solution (WalterEgo.slnx) with the seven packages (no public API yet), one test project per package, repository architecture tests, a benchmark project and a minimal API sample.
  • Build settings: warnings as errors, latest-Recommended analyzers, code style enforced in the build, public API and banned API analyzers, central package management, MinVer versioning, deterministic builds and symbol packages. The SDK is pinned exactly in global.json.
  • Supply chain: lock files restored in locked mode on CI, NuGet audit, nuget.config with package source mapping (nuget.org only), every action pinned to a commit SHA, read-only token by default, Dependabot for NuGet and GitHub Actions, CodeQL (C# and Actions) and OpenSSF Scorecard.
  • CI: build and tests on Linux and Windows (tests that need Docker run on Linux only), coverage summary, dotnet format, package checks, pull request title and internal-reference checks that also run when the pull request is edited, and a check that contract changes come with sample updates.
  • Repository files: license, security policy (with the WalterEgo-specific scope), contributing guide, changelog and the README in English and Portuguese.

How it was tested

  • dotnet build -c Release: 0 warnings, 0 errors.
  • dotnet test: 109 passed. The architecture tests cover the solution inventory, build settings, analyzer wiring, the dependency allowlist of each package, internal references in versioned files, the ignored local folder, lock files, NuGet sources, workflows and repository files.
  • dotnet format --verify-no-changes: clean.
  • dotnet pack: 7 packages and 7 symbol packages sharing one prerelease version (0.1.0-alpha.0.4 locally).
  • The CI scripts were exercised against positive and negative scenarios: pull request title, internal references in title, description and commits, contract changes with and without sample updates or the no-sample-impact label, and package counts. A locked restore fails with NU1004 when a package version changes without its lock file. Every entry of the banned API list was checked to trigger the analyzer.

Public API impact

None: the packages contain no public types yet.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@net0well
net0well merged commit e25c463 into main Oct 21, 2026
10 of 14 checks passed
@net0well
net0well deleted the build/solution-foundation branch October 21, 2026 20:53
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.

2 participants