Skip to content

Latest commit

 

History

History
89 lines (62 loc) · 4 KB

File metadata and controls

89 lines (62 loc) · 4 KB

Contributing to Payroll Engine

Thank you for your interest in contributing to the Payroll Engine! This document describes how you can get involved.

🚧 The Payroll Engine is currently in pre-release (0.y.z). Breaking changes are possible at any time until version 1.0. Please keep this in mind before starting any larger contribution.

Ways to Contribute

Community contributions are currently welcome in the following areas:

Area Description
Docker Improvements to the Docker Compose stack
CI/CD CI/CD integrations across the repositories
Linux Setup Running and setting up the engine on Linux
Web App Localization Translations for the web application
Alternative Databases Persistence layer implementations for databases other than SQL Server (see SQL Server implementation as reference)

If you are interested in working on one of these areas, please contact us before starting, so we can coordinate and avoid duplicate effort.

Reporting Issues

Use GitHub Issues to report bugs or unexpected behavior. Please include:

  • A clear description of the problem
  • Steps to reproduce
  • Expected vs. actual behavior
  • Environment details (.NET version, OS, Docker version if applicable)

For security vulnerabilities, do not open a public issue — see SECURITY.md for the responsible disclosure process.

Suggesting Features and Asking Questions

Use GitHub Discussions for feature suggestions, questions, and general feedback. This is the preferred channel for open-ended topics that are not yet actionable as issues.

Pull Requests

Before opening a pull request, please:

  1. Open an issue or discussion to align on the approach
  2. Ensure your changes are consistent with the existing code style (.NET / C#)
  3. Add or update tests where applicable
  4. Keep commits focused and well-described

All contributions must be compatible with the MIT License.

Development Prerequisites

Code Quality

The repositories use .editorconfig and Roslyn Analyzers to enforce a consistent code style. All analyzer warnings are treated as errors — your build must be warning-free before opening a pull request.

Recommended tooling:

Both tools surface the same analyzer violations that the CI build enforces. Using one of them locally saves review cycles.

Code of Conduct

This project follows the Contributor Covenant Code of Conduct. By participating, you are expected to uphold these standards.

Contact