We love your input! We want to make contributing to gcorelabscloud-go as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
- Fork the repo and create your branch from
master - If you've added code that should be tested, add tests
- If you've changed APIs, update the documentation
- Make sure your code follows the existing style
- Issue that pull request!
- Install Go 1.21 or later
- Clone the repository:
git clone https://github.com/G-Core/gcorelabscloud-go.git cd gcorelabscloud-go - Install dependencies:
go mod download
- Follow standard Go conventions and Effective Go
- Include comments on exported functions and types
- Add tests for any new code you write
- Tests should be clear and maintainable
- Update the README.md with details of changes to the interface, if applicable
- Update any relevant documentation
- The PR will be merged once you have the sign-off of at least one maintainer
In short, when you submit code changes, your submissions are understood to be under the same Mozilla Public License Version 2.0 that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using GitHub's issue tracker
We use GitHub issues to track public bugs. Report a bug by opening a new issue.
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
By contributing, you agree that your contributions will be licensed under its Mozilla Public License Version 2.0.