***********************
Contributing Guidelines
***********************

Thank you for considering a contribution to the Erbsland Configuration Parser for C++! We're grateful for your interest and appreciate your time and effort.

Code of Conduct
===============

By contributing to this project, you agree to follow our :doc:`Code of Conduct<code-of-conduct>`. Please take a moment to read it. It helps us maintain a welcoming, respectful, and inclusive space for everyone.

See: :doc:`code-of-conduct`.

How You Can Contribute
======================

We welcome your input in many forms:

- **Found a bug?** Please `open an issue <https://github.com/erbsland-dev/erbsland-cpp-configuration/issues/new>`_ to let us know.
- **Have a feature request?** We’re happy to hear your ideas—please `open an issue <https://github.com/erbsland-dev/erbsland-cpp-configuration/issues/new>`_.
- **Have a question?** Feel free to `start a discussion <https://github.com/erbsland-dev/erbsland-cpp-configuration/discussions>`_``. We’re glad to help!

Pull Requests
=============

Before submitting a pull request, please first connect with us by starting a `discussion <https://github.com/erbsland-dev/erbsland-cpp-configuration/discussions>`_ or by `opening an issue <https://github.com/erbsland-dev/erbsland-cpp-configuration/issues/new>`_. This helps us align efforts and keep things moving smoothly.

See also: :doc:`code-style` and :doc:`write-a-unittest`.

About the Use of Artificial Intelligence
========================================

We value contributions that are thoughtfully crafted. While it's okay to use tools to improve the clarity of your text or code, we expect all contributions to be reviewed by a human before submission.

We regularly scan the codebase for vulnerabilities and similar issues using automated tools. These are handled internally and are not tracked publicly. Automatically generated issues or pull requests without meaningful human input will not be accepted.

.. toctree::
    :maxdepth: 3
    :hidden:

    code-of-conduct
    code-style
    write-a-unittest