Contributing Guidelines
Thank you for considering a contribution to the Erbsland Configuration Parser for Python! We truly appreciate your time and effort, and we’re excited to collaborate with you.
Code of Conduct
By contributing to this project, you agree to follow our Code of Conduct. Please take a moment to read it—it helps us maintain a welcoming, respectful, and inclusive community for everyone.
How You Can Contribute
We welcome contributions of all kinds. Here are a few ways to get involved:
Found a bug? Please open an issue to let us know.
Have a feature request? We’d love to hear your ideas—just open an issue.
Have a question? Feel free to start a discussion. We’re glad to help!
Even small contributions, such as improving documentation, fixing typos, or clarifying error messages, are valuable and appreciated.
Pull Requests
We encourage pull requests, but to avoid duplicate work and make sure we’re aligned, please reach out first by:
starting a discussion, or
This helps us review your idea early and ensure your contribution fits well into the project’s direction.
Before submitting, please also review:
ErbslandDEV Python Code Style for our Python coding conventions.
How to Write a New Unit Test for writing and running tests.
Well-tested, clean, and documented contributions have the best chance of being merged quickly.
About the Use of Artificial Intelligence
We value contributions that are thoughtfully crafted by humans. Using tools to improve clarity or catch mistakes is perfectly fine, but all contributions must be reviewed and validated by you before submission.
To keep the project safe and maintainable:
We regularly scan the codebase for vulnerabilities and similar issues with automated tools.
Automatically generated issues or pull requests without meaningful human input will not be accepted.
Our goal is to keep this project reliable, transparent, and easy to contribute to—for everyone.