Thank you for your interest in contributing to bevy-discord! This document will guide you through
the contribution process.
If you discover a security vulnerability, please DO NOT open a public issue. Instead, email the details to [email protected].
- First, check if the issue has already been reported
- If not, create a new issue with:
- A clear, descriptive title
- A detailed description of the problem
- Steps to reproduce the issue
- Expected vs actual behaviour
- Any relevant screeshots or error messages
- Visit our discussions page
- Search for similar topics
- Create a new discussion if your topic hasn't been addressed
- Fork the repository
- Create a new branch for your fix
- Submit a Pull Request with:
- Clear description of the problem and solution
- Reference to related issue(s) if applicable
- Updated tests/examples if necessary
- Before writing code for a new feature:
- Propose your idea in the ideas category
- Wait for community feedback and maintainer approval
- Only start implementation after receiving positive feedback
- We do not accept purely cosmetic changes (whitespace, formatting, etc.)
- Focus on changes that improve:
- Stablity
- Functionality
- Testability
- Maintainer: Aditya Kumar
- Email: [email protected]
- GitHub Discussions: bevy-discord/discussions
Thank you for contributing to making bevy-discord better!