47 lines
2.7 KiB
Markdown
47 lines
2.7 KiB
Markdown
# RPEmotes - Contributing Guidelines
|
|
|
|
Thank you for considering contributing to our project! We value the involvement of every community member and appreciate your help in making this project better. To ensure a positive and inclusive experience for everyone, we have established these guidelines, which we expect all contributors to follow.
|
|
|
|
## Code of Conduct
|
|
|
|
Before contributing, please review our [Code of Conduct](CODE_OF_CONDUCT.md) to understand the expected behavior and our commitment to maintaining a respectful and inclusive environment.
|
|
|
|
## How to Contribute
|
|
|
|
1. Fork the repository and create your branch from the `master` branch.
|
|
2. Ensure that your code follows our coding conventions and style guidelines.
|
|
3. Make your changes, including tests if applicable, and ensure that the code compiles successfully.
|
|
4. Commit your changes and provide a clear and descriptive commit message.
|
|
5. Push your branch to your forked repository.
|
|
6. Submit a pull request to the `master` branch of the main repository.
|
|
7. Be responsive to any feedback or questions that may arise during the review process.
|
|
|
|
## Communication
|
|
|
|
- If you have questions or need clarification, feel free to open an issue in the repository.
|
|
- Use respectful and inclusive language in all communications.
|
|
- Be open to feedback and be constructive in your responses.
|
|
|
|
## Reporting Issues
|
|
|
|
- If you encounter any issues or have suggestions for improvement, please check the issue tracker to see if it has already been reported.
|
|
- If the issue is new, feel free to open a new issue, providing a clear and descriptive title and description.
|
|
- Include as much relevant information as possible to help us understand and address the issue more efficiently.
|
|
- Be respectful to others when commenting on existing issues.
|
|
|
|
## Pull Request Guidelines
|
|
|
|
- Before submitting a pull request, make sure that your changes address the problem or feature request effectively.
|
|
- Provide a clear and descriptive title for your pull request.
|
|
- Include a summary of the changes made and any additional information that may be helpful for the reviewer.
|
|
- Ensure that your code is well-documented and tested, when applicable.
|
|
- Be open to feedback and be responsive to any requests for changes or improvements.
|
|
|
|
## Attribution
|
|
|
|
These Contributing Guidelines are adapted from the [Open Source Guide](https://opensource.guide/), available at [https://opensource.guide/starting-a-project/#writing-contributor-guidelines](https://opensource.guide/starting-a-project/#writing-contributor-guidelines).
|
|
|
|
## Acknowledgment
|
|
|
|
We appreciate the time and effort you put into contributing to this project. Your contributions help make this project better for everyone involved. Thank you for being a part of our community!
|
|
|