Thank you for your interest in contributing to MuleTalks! We welcome contributions from everyone who wants to help improve our public assets. This document provides guidelines to make the contribution process smooth and effective.
Please review and adhere to our Code of Conduct to ensure a welcoming and respectful environment for all contributors.
- Check existing issues to avoid duplicates.
- Use a clear and descriptive title.
- Provide detailed information, including steps to reproduce, expected behavior, and actual behavior.
- Fork the repository.
- Create a new branch for your changes.
- Make your changes following our coding standards.
- Commit your changes with a clear and descriptive commit message.
- Submit a pull request, referencing any related issues.
- Ensure that your code passes any existing tests and includes new tests if applicable.
- Ensure that all code, examples, and assets are well-documented.
- Follow the existing structure and formatting.
- Use clear and concise language.
- All contributions will be reviewed by the maintainers.
- Feedback and requested changes should be addressed promptly.
- Once approved, contributions will be merged into the main branch.
If you have any questions or need assistance, please don't hesitate to reach out by opening an issue or contacting us directly at contact@muletalks.dev.
By contributing to MuleTalks, you agree that your contributions will be licensed under the same terms as the LICENSE file in this repository.
Thank you for taking the time to contribute to MuleTalks. Your efforts help us create a valuable resource for the MuleSoft community. Together, we can make a difference!