We love your input! We want to make contributing to this project 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
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
- Read effective go as it's a great starting point.
- Then read OpenTelemetry's coding guidelines as we generally follow this.
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
Explain that when someone submits a contribution, they are agreeing that the project owner can use their contribution under the project's license.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
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)
TODO: Detail the style guide and coding conventions further, if needed.
After making a code change, run the make checks
command to validate that all
code is formatted, tested, etc. successfully:
New components can be created by running compgen. See compgen's README for instructions and guidance.
By contributing, you agree that your contributions will be licensed under its [License Name].
Include any references or resources that might be helpful for the contributor.
Thank you for considering contributing to liatrio-otel-collector!