We adopted the Contributor Covenant as the Code of Conduct of our projects.
We have adopted rules on the use and nomenclature of branches. These rules are inspired from the Gitflow and GitHub flow workflows.
This branch contains the latest stable version. This branch is subject to restrictions.
This branch contains the version under development. This branch is subject to restrictions.
It is created from and merge in main.
These branches correspond to the correction of a critical bug.
They are created from and merge in main.
These branches correspond to the correction of a bug.
They are created from and merge in develop.
These branches correspond to the development of a feature or an improvement.
They are created from and merge in develop.
We have adopted the Conventional Commit as our commit message standard. It helps maintain a clear and accurate history of changes made.
Before submitting a new issue, make sure there are no similar ones to yours, open or not. If a similar issue exists, comment only if you have additional information that would be useful in resolving it. If not, open a new issue and follow the template steps.
Before submitting a new pull request, make sure there are no existing features or pull requests similar to yours. If a similar pull request exists, contribute only if you have useful features to add to it. If not, follow these steps:
- Open a new issue by following the Issue section
- Fork the repository
- Create a new branch by following the Branch section of the Git Guidelines
git checkout -b <branch-name>- Make your changes by following the project Code Guidelines
- Commit your changes by following the Commit section of the Git Guidelines
- Push your branch
git push <branch-name>- Create a new pull request and follow the template steps.