Skip to content

Latest commit

 

History

History
33 lines (24 loc) · 1.57 KB

CONTRIBUTING.md

File metadata and controls

33 lines (24 loc) · 1.57 KB

Contributing to ReactiveVi4

We love your response! We want to make contributing to this project as easy , whether it's:

  • Reporting a bug
  • Discussing the current state of the code
  • Submitting a fix
  • Proposing new features

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:

  1. Fork the repo and create your branch from features.
  2. If you've added code that should be tested, add tests.
  3. Update the documentation.
  4. Write Examples from basic to advanced
  5. Issue that pull request to features branch

Any contributions you make will be under the MIT Software License

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.

Report bugs using Github's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Write bug reports with detail, background, and sample code

This is an example of a bug report.

Use PHPStan and CS-fix

License

By contributing, you agree that your contributions will be licensed under its MIT License.

References

This document was adapted from the open-source contribution guidelines