First off, thanks for taking the time to contribute! π
The following is a set of guidelines for contributing to projects in the POps-Rox organization. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code.
Before creating bug reports, please check existing issues to avoid duplicates. When you create a bug report, include as many details as possible using our bug report template.
Feature suggestions are tracked as GitHub issues. Create an issue using the feature request template and provide:
- A clear and descriptive title
- A detailed description of the suggested feature
- Any possible alternatives you've considered
- Why this feature would be useful
- Fork the repository
- Create a feature branch from
main:git checkout -b feature/my-feature - Make your changes with clear, descriptive commit messages
- Test your changes thoroughly
- Push to your fork:
git push origin feature/my-feature - Open a Pull Request against
main
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests after the first line
See the repository's README for specific setup instructions.
- Run
terraform fmtbefore committing - Use meaningful variable and resource names
- Include descriptions for all variables and outputs
- Provide examples in an
examples/directory
- Follow the existing code style in the project
- Comment your code where the intent isn't obvious
- Update documentation alongside code changes
By contributing, you agree that your contributions will be licensed under the MIT License.