Thanks for your interest in contributing to ForgeFlow! This document provides guidelines for contributing to the project.
- Fork the repository
- Clone your fork:
git clone https://github.com/YOUR_USERNAME/ForgeFlow.git - Create a feature branch:
git checkout -b feature/your-feature-name - Make your changes
- Test your changes thoroughly
- Commit with clear messages:
git commit -m "Add: feature description" - Push to your fork:
git push origin feature/your-feature-name - Open a Pull Request
- Go 1.21+
- Node.js 20+
- Wails CLI
# Install dependencies and run dev server
wails dev
# Frontend only
cd frontend && npm run dev- Use TypeScript strict mode
- Prefer functional components with hooks
- Use Zustand for state management
- Follow Tailwind CSS utility-first approach
- Use oklch colors for theming
- Follow standard Go conventions
- Run
go fmtbefore committing - Add comments for exported functions
Use clear, descriptive commit messages:
Add:for new featuresFix:for bug fixesUpdate:for changes to existing featuresRefactor:for code refactoringDocs:for documentation changes
- Keep PRs focused on a single feature or fix
- Update documentation if needed
- Add tests if applicable
- Ensure all tests pass
- Reference related issues
When reporting bugs, please include:
- ForgeFlow version
- Operating system
- Steps to reproduce
- Expected vs actual behavior
- Screenshots if applicable
We welcome feature requests! Please:
- Check existing issues first
- Describe the use case
- Explain why it would be useful
- Consider implementation complexity
Feel free to open an issue for questions or join discussions.
Thank you for contributing to ForgeFlow! 🚀