Skip to content

Contribution Rule

μœ μ’…λ¬Έ edited this page May 26, 2024 · 3 revisions

Contribution Guidelines

Thank you for considering contributing to our project! We welcome all kinds of contributions, from code and documentation improvements to bug reports and feature requests.

How to Contribute

🐞 Reporting Bugs

If you find a bug, please report it by opening an issue in the GitHub repository. Please include:

  • A clear and descriptive title.
  • A detailed description of the problem.
  • Steps to reproduce the issue.
  • Any relevant screenshots or logs.

✨ Suggesting Features

We are always looking for new ideas to improve our project. If you have a suggestion for a new feature, please open an issue and include:

  • A clear and descriptive title.
  • A detailed description of the proposed feature.
  • Any potential use cases or examples.

🍻 Code Contributions

We follow a standard Git workflow. Here’s how you can contribute code:

  1. Fork the Repository: Click the 'Fork' button at the top right corner of the repository page.
  2. Clone the Forked Repository: Clone your forked repository to your local machine.
    git clone https://github.com/your-username/repository-name.git
  3. Create a Branch: Create a new branch for your feature or bug fix.
    git checkout -b feature/your-feature-name
  4. Make Changes: Make your changes in the codebase.
  5. Commit Changes: Commit your changes with a clear and descriptive commit message.
    git add .
    git commit -m "Add feature/fix bug: detailed description of your changes"
  6. Push to the Branch: Push your changes to the branch in your forked repository.
    git push origin feature/your-feature-name
  7. Create a Pull Request: Open a pull request to the main repository. Please ensure your pull request includes:
    • A clear and descriptive title.
    • A detailed description of the changes.
    • Any relevant issues or context.

πŸ₯° Code Style

Please ensure your code adheres to our coding standards:

  • Follow the existing code style and structure.
  • Write clear, concise, and well-documented code.
  • Include comments to explain the logic and decisions behind complex sections.

πŸ“‘ Documentation

Contributions to documentation are highly valued. Please ensure that:

  • Documentation is clear, concise, and easy to understand.
  • Any new features or changes are well-documented.
  • Code examples are included where applicable.

😎 Review Process

All contributions will go through a review process:

  • A project maintainer will review your pull request.
  • Feedback will be provided, and changes may be requested.
  • Once approved, your pull request will be merged into the main branch.

πŸ› οΈ Code of Conduct

We expect all contributors to adhere to our Code of Conduct. Please ensure you are respectful and considerate in all interactions.

Getting Help

If you need any help, feel free to reach out by opening an issue or contacting one of the project maintainers.

Thank you for your contributions and for helping us improve this project!

Clone this wiki locally