Create a feature branch for repository changes and open a pull request against master.
Do not push directly to master unless the repository owner explicitly asks for a direct push for that specific change.
Keep pull requests ready for automated CI checks and Claude/Codex review before merge.
Use the commands below before opening a pull request.
dotnet test ./DomainDetective.Tests/DomainDetective.Tests.csproj --configuration Release --framework net10.0
dotnet test ./DomainDetective.CLI.Tests/DomainDetective.CLI.Tests.csproj --configuration Release --framework net10.0Run these when a change affects the public site, Blazor tools app, navigation, wording, or GitHub Pages/static behavior.
dotnet test ./DomainDetective.Website.Tests/DomainDetective.Website.Tests.csproj --configuration Release --framework net10.0
dotnet build ./DomainDetective.Website/DomainDetective.Website.csproj
pwsh ./Website/build.ps1 -FastWebsitecontains the static marketing/docs/API siteDomainDetective.Websitecontains the Blazor WebAssembly tools appDomainDetective.Toolboxcontains the shared website/tooling componentsDomainDetective.Website.Testscontains helper, component, page, and layout regression tests for the website experience
.github/workflows/dotnet-tests.ymlruns the .NET test matrix and includesDomainDetective.Website.Testson thenet10.0lane.github/workflows/website-ci.ymlruns website regression tests before the PowerForge website build on pull requests.github/workflows/deploy-website.ymldeploys the website and also reacts toDomainDetective.Website/**andDomainDetective.Toolbox/**changes
Website-related CI is triggered by changes in:
Website/**DomainDetective.Website/**DomainDetective.Toolbox/**DomainDetective.Website.Tests/**
- A static-only deployment such as GitHub Pages does not provide
/tool-api - Production-style hosted tool checks should be validated through
DomainDetective.OnlineHost