chore: CONTRIBUTING.md added

[samtrion]

Summary by CodeRabbit

• Documentation
  • Added comprehensive contribution guidelines covering expected communication (English), trunk-based workflow, project structure, testing conventions, centralized dependency versioning, commit message format (Conventional Commits), development steps (restore/build/test/format), PR requirements (summary, motivation, related issues, test results), and guidance for dependency updates.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Adds a new CONTRIBUTING.md that defines contribution guidelines: language and workflow expectations, project/test layout, central version management via Directory.Packages.props, Conventional Commits 1.0.0 commit format, build/test/format commands, PR requirements, and dependency update guidance including Renovate Bot.

Changes

Cohort / File(s)

Summary

Documentation CONTRIBUTING.md

New file describing contribution guidelines: English usage, trunk-based workflow, project structure (src/, tests/), test project naming, central versioning via Directory.Packages.props, Conventional Commits 1.0.0 commit format, development commands (dotnet restore/build/test), code formatting with csharpier, PR content requirements, and dependency update practices (Renovate Bot and manual central updates).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Pure documentation addition — no code or API changes.
• Verify wording matches actual project practices and tooling (e.g., csharpier, Directory.Packages.props).
• Confirm no contradictory guidance with repository config.

Poem

🐇 I hopped through lines to write what to do,
Commit with care and trunk-based true,
Tests in their homes and versions held tight,
Renovate knocks and PRs take flight,
Welcome, friend — nibble code by moonlight. ✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a CONTRIBUTING.md file with contribution guidelines to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 3e5ea22 and 08f09af.

📒 Files selected for processing (1)

• CONTRIBUTING.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• CONTRIBUTING.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between c51a849 and 3e5ea22.

📒 Files selected for processing (1)

• CONTRIBUTING.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

CONTRIBUTING.md

15-15: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (1)

CONTRIBUTING.md (1)

1-38: Comprehensive and well-structured contribution guidelines.

The CONTRIBUTING.md file provides clear, actionable guidance on commit conventions (Conventional Commits 1.0.0), project structure, development workflow, pull request expectations, and dependency management. The guidelines are specific and practical—from enforcing centralized version management via Directory.Packages.props to referencing tools like Renovate Bot and CSharpier. The expectations section effectively communicates the repository's trunk-based workflow and English-language requirement.