We want to make contributing to this project as easy and transparent as possible.
We actively welcome your pull requests. When we get one, we'll run some Parse-specific integration tests on it first. From here, we'll need to get a core member to sign off on the changes and then merge the pull request. For API changes we may need to fix internal uses, which could cause some delay. We'll do our best to provide updates and feedback throughout the process.
- Fork the repo and create your branch from
master. - Add unit tests for any new code you add.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Follow the commit message format for automated versioning (see below).
- For dependency updates, see the Dependency Management section.
The Parse SDK follows a structured approach to dependency management. See VERSIONING_POLICY.md for full details.
The Parse SDK supports Dart and Flutter versions for 6 months after the next significant version release. When contributing:
- Ensure compatibility with all supported versions (see README compatibility tables)
- Don't use features only available in the latest version without version checks
- CI will test your PR against all supported versions
This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to honor this code.
By contributing to Parse SDK Flutter, you agree that your contributions will be licensed under its license.