Thank you for your interest in contributing to Hexal! This document provides guidelines and information for contributors.
Before submitting a bug report:
- Check the existing issues to avoid duplicates
- Use the bug report template when creating a new issue
- Include as much detail as possible:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Screenshots if applicable
- Your OS and Hexal version
- Check existing issues and discussions for similar suggestions
- Use the feature request template
- Clearly describe the use case and expected behavior
- Fork the repository
- Create a feature branch from
main:git checkout -b feature/your-feature-name
- Make your changes following the code style guidelines
- Test your changes thoroughly
- Commit with clear, descriptive messages
- Push to your fork and submit a pull request
# Clone your fork
git clone https://github.com/YOUR_USERNAME/hexal.git
cd hexal/hexal-electron
# Install dependencies
npm install
# Start development server
npm run dev- Use TypeScript for all new code
- Follow existing patterns in the codebase
- Use meaningful variable and function names
- Add comments for complex logic
- Keep components focused and modular
- Components go in
src/components/ - State management in
src/stores/ - Utility functions in
src/services/ - Type definitions in
src/types/ - Styles in
src/styles/
Use conventional commit format:
feat:for new featuresfix:for bug fixesdocs:for documentation changesrefactor:for code refactoringtest:for adding testschore:for maintenance tasks
Example: feat: add weather simulation system
Feel free to open an issue for any questions about contributing.