Thank you for contributing to our projects! This guide helps us keep everything clean, organized, and easy to understand.
- Fork the repository before making changes.
- Work in your own feature branch, not directly in the
mainbranch. - Write clear and meaningful commit messages.
- Make sure your code follows the existing code style.
- main – stable production code
- testbereich – bug fixes and testing new features
- Keep branch names short and descriptive.
- Push your changes to your feature branch.
- Open a pull request (PR) targeting
testing area. - Clearly describe what was changed and why.
- Ensure there are no errors or merge conflicts.
- A PR will only be merged after review by an Administrator or Owner.
- Create an issue before opening a PR if you are proposing a new feature or bug fix.
- Describe the problem or improvement as clearly as possible.
- HTML / CSS / JS: Follow common best practices and the existing project style.
- PHP: Use clean and readable syntax and follow existing conventions.
- Add comments where the code is not immediately understandable.
- Remove unnecessary debug output before merging.
- Add new tests for your features or bug fixes whenever possible.
- Make sure existing tests do not fail.
We appreciate every contribution!
With your help, Nexory becomes better, cleaner, and more professional. 🚀