Thank you for your interest in contributing to the Go Projects Toolkit! This document provides guidelines and instructions for contributing.
If you find a bug, please create an issue on GitHub with:
- A clear and descriptive title
- A detailed description of the problem
- Steps to reproduce the issue
- Expected behavior vs. actual behavior
- Any relevant code snippets or error messages
If you have an idea for a new feature or improvement:
- Check if there's already an issue or pull request for it
- Create a new issue describing your suggestion
- Explain why the enhancement would be useful
- Fork the repository
- Create a new branch for your feature or bug fix
- Make your changes
- Ensure your code follows the existing style
- Add or update tests as necessary
- Update documentation if needed
- Submit a pull request
- Follow the official Go Code Review Comments
- Use
gofmtto format your code - Write clear, concise comments
- Use meaningful variable and function names
- Keep functions small and focused
- Ensure all existing tests pass
- Add new tests for any new functionality
- Test your changes on multiple platforms if possible
- Update README files when adding new features
- Keep documentation clear and concise
- Include examples when appropriate
- Ensure your code compiles and passes tests
- Update the README.md with details of changes if applicable
- Increase the version number in any examples if needed
- Your pull request will be reviewed by maintainers
- Address any feedback during the review process
If you have any questions about contributing, feel free to create an issue asking for clarification.
Thank you for helping make the Go Projects Toolkit better!