Skip to content

Latest commit

 

History

History
45 lines (30 loc) · 2.17 KB

CONTRIBUTING.md

File metadata and controls

45 lines (30 loc) · 2.17 KB
Raw

Contributing to @smakss/react-scroll-direction

First and foremost, thank you for considering contributing to @smakss/react-scroll-direction! Your efforts help make this project better for everyone.

Getting Started

  • Please first discuss the change you wish to make via issue, email, or any other method with the maintainers of this repository before making a change.
  • Ensure that your contribution is in line with the project's coding and documentation standards.

Development Setup

Before you start working on your contribution, you need to set up your development environment. After cloning the repository, run the following commands:

yarn setup

This will install all the necessary development dependencies and set up Git hooks using Husky.

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  2. Update the README.md or relevant documentation with details of changes, including:
    • New environment variables
    • New database migrations
    • Any other relevant information
  3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is SemVer.
  4. Ensure your PR has a single purpose. If it addresses more than one issue or introduces more than one feature, split them into separate PRs.
  5. Describe your PR thoroughly. Explain the purpose of your PR, how you approached the problem, and include any relevant information or screenshots for context.

Coding Standards

  • Follow Typescript specific conventions and @smakss/react-scroll-direction's established coding style.
  • Write tests for any new functionality.
  • Comment your code where necessary.

Reporting Issues

  • Use the provided issue templates if applicable.
  • Be as descriptive as possible. Attach screenshots, logs, or any other relevant information.
  • Check existing issues before submitting a new one to avoid duplicates.

Code of Conduct

Please refer to our Code of Conduct to understand what kind of behavior is expected within our community.