Skip to content

Latest commit

 

History

History
62 lines (39 loc) · 3 KB

CONTRIBUTING.md

File metadata and controls

62 lines (39 loc) · 3 KB
Raw

Contributing to MailPilot

First of all, thank you for considering contributing to MailPilot! Your help is greatly appreciated.

The following is a set of guidelines for contributing to MailPilot. These are just guidelines, not rules, so use your best judgment and feel free to propose changes to this document in a pull request.

Table of Contents

How Can I Contribute?

There are several ways you can contribute to MailPilot:

  • Reporting Bugs: If you encounter any issues with MailPilot, please report them by opening an issue.

  • Requesting Features: If you have ideas for new features or improvements, please open an issue to discuss them.

  • Code Contribution: You can contribute to the development of MailPilot by submitting pull requests with bug fixes, improvements, or new features.

  • Documentation Contribution: Help improve our documentation by suggesting edits or additions.

Code of Conduct

This project and everyone participating in it are governed by the MailPilot Code of Conduct. By participating, you are expected to uphold this code. Please report any unacceptable behavior to contact@plawlost.com.

Reporting Bugs

If you encounter a bug in MailPilot, please open an issue to report it. When reporting bugs, please include as much information as possible, such as the steps to reproduce the issue, the error messages, and your system environment.

Requesting Features

If you have an idea for a new feature or an improvement, please open an issue to discuss it. We appreciate your input and feedback.

Code Contribution

Before contributing code, please follow these guidelines:

Pull Request Guidelines

  • Create a fork of the MailPilot repository.
  • Create a branch for your changes: git checkout -b feature/your-feature-name.
  • Make your changes, ensuring that your code follows the project's coding style and conventions.
  • Test your changes thoroughly.
  • Commit your changes with clear and concise commit messages.
  • Push your branch to your fork: git push origin feature/your-feature-name.
  • Create a pull request to the main MailPilot repository's main branch.

Documentation Contribution

Improvements to the documentation are always welcome. If you find any issues or have suggestions for improvements, please submit a pull request or open an issue on GitHub.

License

By contributing to MailPilot, you agree that your contributions will be licensed under the Apache License 2.0.