Contributing to TaskTide¶
Contributions are welcome.¶
Before Contributing
Please read the project documentation and check existing issues and pull requests before starting significant work.
For larger changes, opening an issue to discuss the proposed approach first is encouraged. This helps avoid duplicated work and ensures that a contribution is aligned with the direction of TaskTide.
Development¶
Please ensure that your changes:
- Build successfully
- Include appropriate tests where applicable
- Do not introduce unrelated changes
- Follow the existing structure and conventions of the project
- Update relevant documentation when behaviour or usage changes
Run the project's test suite before submitting a pull request.
Pull Requests¶
Pull requests should describe:
- What was changed
- Why the change was made
- How the change was tested
- Any relevant limitations or considerations
Keep pull requests focused on a single change where practical.
All pull requests are subject to review. Changes may be requested before a pull request is merged.
Scope and Acceptance¶
Contributions are suggestions to the project, not commitments from the maintainers.
A pull request or issue does not imply that TaskTide will adopt the proposed behaviour, design, dependency, feature, or compatibility requirement.
The maintainers may decline, defer, modify, or close contributions that do not fit the project's scope, design goals, quality standards, or priorities.
TaskTide is developed according to the needs and direction of the project. Contributors are welcome to propose changes, but acceptance remains at the discretion of the maintainers.
Code of Conduct¶
Please keep discussions and contributions respectful and constructive.
Security¶
Please do not report security vulnerabilities through public issues. See "SECURITY.md" for the appropriate reporting process.
