First off, thank you for considering contributing to FreeCustom.Email! It's people like you that make FreeCustom.Email such a great tool.
There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into FreeCustom.Email itself.
This project and everyone participating in it is governed by the FreeCustom.Email Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to dishantsinghdev@icloud.com.
Bugs are tracked as GitHub issues. Before opening a new issue, please check if the bug has already been reported. If it has, please add a comment to the existing issue instead of opening a new one.
When you are creating a bug report, please include as many details as possible. Fill out the required template, the information it asks for helps us resolve issues faster.
Enhancement suggestions are tracked as GitHub issues. Before opening a new issue, please check if the enhancement has already been suggested. If it has, please add a comment to the existing issue instead of opening a new one.
We love pull requests! Here's a quick guide:
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
- Use the present tense ("Add feature" not "Added feature").
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...").
- Limit the first line to 72 characters or less.
- Reference issues and pull requests liberally after the first line.
We use Prettier and ESLint to maintain a consistent code style. Please run npm run lint and npm run format before submitting a pull request.
By contributing, you agree that your contributions will be licensed under its Apache License 2.0.