First off, thanks for taking the time to contribute! 🎉
The following is a set of guidelines for contributing to this project. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code.
This section guides you through submitting a bug report for ECS Discord Bot. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- Check the issue tracker to see if the issue has already been reported.
- Perform a search to see if the issue has been addressed in other ways.
Bugs are tracked as GitHub issues. After you've determined that your bug is new, create an issue and provide the following information:
- Use a clear and descriptive title.
- Describe the steps to reproduce the problem.
- Provide specific examples to demonstrate the steps.
- Describe the behavior you observed and what you expected to see.
- Include screenshots and animated GIFs if applicable.
- Specify which version of the project you're using.
This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to an existing functionality.
- Check the issue tracker to see if the enhancement has already been suggested.
- Perform a search to see if the enhancement or a similar one has been proposed.
Enhancement suggestions are tracked as GitHub issues. After you've determined that your enhancement is new, create an issue and provide the following information:
- Use a clear and descriptive title.
- Provide a step-by-step description of the suggested enhancement.
- Explain why this enhancement would be useful.
- Include any relevant examples, screenshots, or references.
- Fork the repository.
- Clone your fork to your local machine.
- Create a new branch:
git checkout -b my-branch-name
. - Make your changes and commit them.
- Push to your fork and submit a pull request.
- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
- 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.