First off, thank you for considering contributing to the OpenTelemetry Cheat Sheet! It's people like you that make this resource valuable for the community.
If you find a bug in any of the configuration examples or documentation:
- Use the GitHub issue search — check if the issue has already been reported.
- If the issue hasn't been reported, create a new issue.
- Clearly describe the issue, including steps to reproduce when it is a bug.
If you have an idea for a new feature or an improvement:
- Check the GitHub issues to see if it's already been suggested.
- If not, create a new issue.
- Use a clear and descriptive title.
- Provide a detailed description of the suggested enhancement.
- Explain why this enhancement would be useful to most users.
- Fork the repo and create your branch from
master
. - If you've added code, add examples or tests as appropriate.
- Ensure your code follows the existing style.
- Write a good commit message.
- Use 2 spaces for indentation.
- Add comments to explain complex configurations.
- Use proper header hierarchy (# for main title, ## for sections, etc.).
- Use code blocks with language specification for code snippets.
- Keep line length to a maximum of 120 characters for better readability.
When adding new examples:
- Create a new directory if it's a new category.
- Include a README.md in the directory explaining the examples.
- Follow the existing naming conventions.
- Ensure your examples are well-commented and easy to understand.
- Keep the main README.md up to date with any new sections or major changes.
- Ensure all links are working.
- Proofread your contributions for spelling and grammar.
- Be welcoming to newcomers and encourage diverse new contributors from all backgrounds.
- Be respectful to others in all communications.
If you have any questions, create an issue (prefixed with [QUESTION]
) or contact the project maintainers.
Thank you for contributing to the OpenTelemetry Cheat Sheet!