Thank you for your interest in contributing to SimplePanel-CS2! This document provides guidelines and standards for contributing to the project.
By participating in this project, you commit to maintaining a respectful and welcoming environment for all contributors.
If you find a bug, please:
- Check that the bug hasn't already been reported in Issues
- Create a new issue with the tag
[BUG]and include:- A clear, descriptive title
- Detailed steps to reproduce the issue
- Expected behavior vs actual behavior
- Environment information (OS, Node.js version, browser, etc.)
- Screenshots or error logs if applicable
If you find a security vulnerability, please DO NOT report it publicly. Instead, contact the repository owner directly through GitHub.
Suggestions for new features and improvements are welcome! Please follow these steps:
- Check existing issues to ensure your suggestion hasn't already been proposed
- Open an issue with the
[SUG]tag and include:- A clear description of the proposed feature
- The specific problem it solves or value it adds
- How the feature should work and any relevant use cases
- Examples, references, or mockups if available
- Why this enhancement would be useful to the project
- Fork the repository
- Create a branch for your feature:
Or for fixes:
git checkout -b feature/your-feature-name
git checkout -b fix/fix-description
- Make your changes following the code standards
- Commit your changes:
git commit -m "Clear description of your changes"- Use descriptive commit messages
- Mention the issue number if applicable (e.g., "Fix #123: Fixes error in...")
- Push to your fork:
git push origin feature/your-feature-name
- Open a Pull Request:
- Clearly describe the changes made
- Mention any related issues
- Wait for review from the code owner
- Ensure your code follows the project's standards
- Ensure all tests pass (if they exist)
- Update documentation if necessary
- The code owner will review your PR
- There may be change requests - please be receptive to feedback
- Once approved, your PR will be merged
- Follow the existing code style in the project
- Use descriptive names for variables and functions
- Comment complex code when necessary
- Keep functions small and focused
- Use clear and descriptive commit messages
- Suggested format:
type: Brief description- Examples:
feat: Add notification system,fix: Fix form validation error
- Examples:
- Common types:
feat,fix,docs,style,refactor
- Maintain an organized file structure
- Use descriptive file names
- Group related files in appropriate folders
If you have questions about how to contribute, you can:
- Open an issue with the
questionlabel - Review the existing documentation in the README