We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix or a feature
- Proposing new features
- Becoming a maintainer
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We Use Github Flow, So All Code Changes Happen Through Pull Requests
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch from .
- If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
- branch naminge: You should respect this branch naming pattern
- master-[issue-number]-[subject]
- issues:
- you can use provided issues templates according to the kind of issue
- pull requests:
- As issues template is automaticcly generated when you submit one
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Use issues templates relating to what you need
- Backend is a coded with spring boot framework. For code style rules, we use Eclipse default format.
- Frontend is coded in react js, we should respect ECMAscript
By contributing, you agree that your contributions will be licensed under its MIT License. LINCENSE