Skip to content

Latest commit

 

History

History
51 lines (33 loc) · 2.71 KB

CONTRIBUTING.md

File metadata and controls

51 lines (33 loc) · 2.71 KB
Raw

Contributing to react-native-modal-datetime-picker

Contribution to react-native-modal-datetime-picker are warmly welcome!
Before you start, please keep in mind that the goal of this library is to be as consistent as possible with the native behaviour/style guidelines, so it's highly lickely that we won't accept contributions that introduce customization options that goes against the native guidelines.

Development Process

All work on React Native Modal Datetime Picker happens directly on GitHub. Contributors send pull requests which go through a review process.

Working on your first pull request? You can learn how from this free series: How to Contribute to an Open Source Project on GitHub.

  1. Fork the repo and create your branch from master (a guide on how to fork a repository).
  2. Run yarn to install all required dependencies.
  3. Now you are ready to make your changes!

Tests & Verifications

Currently we use eslint with prettier for linting and formatting the code. They are run on CircleCI for all opened pull requests, but you should use them locally when making changes.

  • yarn lint: Run eslint.
  • yarn lint --fix: Run eslint and automatically fix issues. This is useful for correcting code formatting.

Sending a pull request

When you're sending a pull request:

  • Prefer small pull requests focused on one change.
  • Verify that all tests and validations are passing.
  • Follow the pull request template when opening a pull request.

Commit message convention

We prefix our commit messages with one of the following to signify the kind of change:

  • build: Changes that affect the build system or external dependencies.
  • ci, chore: Changes to our CI configuration files and scripts.
  • docs: Documentation only changes.
  • feat: A new feature.
  • fix: A bug fix.
  • perf: A code change that improves performance.
  • refactor: A code change that neither fixes a bug nor adds a feature.
  • style: Changes that do not affect the meaning of the code.
  • test: Adding missing tests or correcting existing tests.

Release process

We use Semantic Release to automatically release new versions of the library when changes are merged into master. Using the commit message convention described above, it will detect if we need to release a patch, minor, or major version of the library.

Reporting issues

You can report issues on our bug tracker. Please search for existing issues and follow the issue template when opening an issue.