-
Notifications
You must be signed in to change notification settings - Fork 0
Development Workflow
Kieron Lanning edited this page Apr 16, 2026
·
2 revisions
The repository uses just for local workflows.
just tools
just restore
just build
just test
just check
just pack
just version
just version-next
just version-bump| Command | Purpose |
|---|---|
just tools |
Restore local .NET tools such as CSharpier |
just restore |
Restore the solution |
just build |
Build the solution |
just test |
Run the real test projects individually |
just check |
Run formatting checks |
just pack |
Create NuGet packages in artifacts/packages
|
just version |
Read the current shared package version |
just version-next |
Compute the next semantic version from tags + conventional commits |
just version-bump |
Write the computed next version into .dotnet/Directory.Build.props
|
The shared package version is centralized in:
/.dotnet/Directory.Build.props
- CI restores tools and packages, then runs check, build, and tests.
- CD restores tools and packages, packs the NuGet packages, checks for duplicate package versions, and publishes to GitHub Packages.
- Integration tests typically require Docker because the repository uses Testcontainers.
- Some provider-specific tests may depend on optional infrastructure availability in the current environment.