Skip to content

Latest commit

 

History

History
54 lines (38 loc) · 2.14 KB

CONTRIBUTING.md

File metadata and controls

54 lines (38 loc) · 2.14 KB

Contributing Guidelines

Thank you for considering contributing to this project! We welcome your ideas, bug reports, and pull requests. By participating in this project

Getting Started

To get started with the project, follow these steps:

  1. Fork the repository and clone it locally.
  2. Install the project dependencies by running npm install.
  3. Start the development server using npm start.

Make sure to check out the project's README for more detailed instructions on setup and development.

Contributing Workflow

To contribute to this project, please follow these steps:

  1. Create a new branch for your contribution:
    • Use a descriptive name for your branch that reflects the feature or bug you are working on.
  2. Make your changes:
    • Write clean, readable, and well-documented code.
    • Follow the code style guidelines mentioned below.
    • Include relevant tests for your changes.
    • Update the documentation if necessary.
  3. Commit your changes:
    • Use clear and concise commit messages.
    • Include a reference to related issues or pull requests.
  4. Push your branch to your forked repository.
  5. Open a pull request:
    • Provide a detailed description of your changes and their purpose.
    • Mention any related issues or pull requests.

Pull Requests

When submitting a pull request, please ensure the following:

  • Your changes are based on the latest commit of the main branch.
  • The pull request title and description clearly describe the purpose and scope of your changes.
  • The pull request includes relevant tests for the changes made.
  • You have tested your changes locally to ensure they do not introduce any regressions or errors.

Code Style

We adhere to a specific code style to maintain consistency throughout the project. Please follow these guidelines when writing code:

  • Use descriptive and meaningful variable, function, and class names.
  • Follow the clean code principles.
  • Write self-explanatory and well-documented code.
  • Use appropriate comments to explain complex logic or tricky parts of the code.
  • Format your code using a consistent indentation style.