Skip to content

Latest commit

 

History

History
38 lines (29 loc) · 1.68 KB

File metadata and controls

38 lines (29 loc) · 1.68 KB

Contributing to Extension Methods

Thank you for considering contributing! We welcome issues, feature requests, and pull requests.

Published and maintained by Mindfire Digital LLP.

Getting Started

  • Fork the repository and create a feature branch from master.
  • Ensure you have a supported .NET SDK installed and can build the solution locally.
  • Run tests locally before submitting changes.

Ways to Contribute

  • Bug reports: Open an issue with steps to reproduce, expected vs actual behavior, and environment details.
  • Feature requests: Describe the problem you’re solving, proposed solution, and alternatives considered.
  • Pull requests: Small, focused PRs are easier to review and merge.

Pull Request Process

  • Keep PRs focused and add tests for new/changed behavior when applicable.
  • Update documentation in Docs/ and README.md as needed.
  • Ensure the CI build passes.
  • Reference related issues using Fixes #<issue-number> or Closes #<issue-number> when applicable.

Code Style

  • Follow standard C#/.NET conventions.
  • Prefer clear, self-explanatory naming and small, composable methods.
  • Include XML documentation for public APIs where appropriate.

Commits & Branches

  • Use conventional commit prefixes when possible (e.g., feat:, fix:, docs:, test:, chore:).
  • Branch naming: feature/<short-name>, fix/<short-name>, or chore/<short-name>.

Testing

  • Add or update unit tests for any behavioral changes.
  • Ensure all tests pass locally before submitting the PR.

Reporting Security Issues