| name | code-review |
|---|---|
| description | Use for PR expectations, review checklist, docs/changelog, and security considerations in contentstack-utils-dotnet. |
- Opening or reviewing a pull request.
- Deciding whether README/CHANGELOG updates or extra tests are required.
- Assessing impact of new dependencies or public API changes.
- Align PRs with the direct release flow
development->master(nostaginggate in the release path). CODEOWNERSmay request reviews from@contentstack/devex-pr-reviewersand security admins for workflow or.snykchanges.
- Behavior: New or changed logic in
Contentstack.Utilsshould have xUnit coverage inContentstack.Utils.Testsunless truly non-functional (e.g. comment-only). - Public API: User-visible changes should update
README.mdandCHANGELOG.mdas appropriate. - Multi-targeting: The library builds netstandard2.0, net47, net472. After API or dependency changes, verify
dotnet buildsucceeds for all target frameworks (or rely on CI). - Dependencies: New or upgraded NuGet packages affect Snyk (
sca-scan.yml) and CodeQL (codeql-analysis.yml). Ensure licenses and advisories are acceptable. - Secrets: Never commit API keys, tokens, or connection strings. CI uses GitHub secrets only.
Teams may use Blocker (must fix before merge), Major (should fix or track), Minor (nit / follow-up)—keep comments actionable.