# Contributing Guidelines
First off, thank you for taking the time to contribute! 🙌
Your help is appreciated and helps make this project better for everyone.
---
## How to Contribute
### 🐛 Reporting Bugs
If you find a bug, please open an issue and include:
- A clear and descriptive title
- Steps to reproduce the issue
- Expected and actual behavior
- Any relevant logs, screenshots, or environment information
### ✨ Suggesting Enhancements
Have an idea for a new feature or improvement?
- Open an issue and describe your suggestion
- Explain the use case and potential benefits
- Optional: propose an implementation strategy
### 🛠️ Submitting Code Changes
To submit a patch or enhancement:
1. Fork the repository
2. Create a new branch (`git checkout -b feature/your-feature-name`)
3. Make your changes
4. Test your changes (if applicable)
5. Open a pull request with a clear description of your changes
### ✅ Code of Conduct
By participating, you agree to uphold our [Code of Conduct](CODE_OF_CONDUCT.md).
---
## Guidelines
- Keep pull requests focused and atomic (one feature or fix per PR).
- Follow any existing code style or formatting conventions.
- Document your code where necessary.
- Include tests when adding new logic (if applicable).
- Use clear, meaningful commit messages (optionally following [Conventional Commits](https://www.conventionalcommits.org/) and using [Gitmoji](https://gitmoji.dev/) for added clarity and consistency).
## 📝 Commit Template
To help you follow the Gitmoji and Conventional Commit format, you can enable the local commit template:
```bash
git config commit.template .github/commit-template.txt
```
---
## Questions?
If you have any questions or need help, feel free to [open an issue](../../issues) or reach out to the maintainers on [Discord](https://discord.gg/HUVtY5gT6s).