CONTRIBUTING.md

Contributing Guidelines

The following is a set of guidelines for contributing to the NGINX Ansible collection. We really appreciate that you are considering contributing!

Table Of Contents

Ask a Question

Getting Started

Contributing

Code Guidelines

• Git Guidelines
• Ansible Guidelines

Code of Conduct

Ask a Question

Don't know how something works? Curious if the role can achieve your desired functionality? Please open an Issue on GitHub with the label question.

Getting Started

Follow our Installation Guide to install Ansible and get ready to use the NGINX Ansible collection.

Project Structure

• The NGINX Ansible collection is written in yaml and supports NGINX Open Source, NGINX Plus and NGINX App Protect.
• The project follows the standard Ansible collection directory structure:
  • The main code is found in roles/ directory (do note that all roles are Git submodules).
  • Sample playbooks and instructions can be found in the playbooks/ directory.

Contributing

Report a Bug

To report a bug, open an issue on GitHub with the label bug using the available bug report issue template. Please ensure the issue has not already been reported.

Suggest an Enhancement

To suggest an enhancement, please create an issue on GitHub with the label enhancement using the available feature issue template.

Open a Pull Request

• Fork the repo, create a branch, implement your changes, submit a PR when your changes are tested and ready for review.
• Fill in our pull request template.

Note: if you'd like to implement a new feature, please consider creating a feature request issue first to start a discussion about the feature.

Code Guidelines

Ansible Guidelines

• Run molecule lint in each role directory to automatically resolve a lot of yaml and Ansible style issues.
• Run molecule test --all in each role directory to catch any other issues.
• Follow these guides on some good practices for Ansible:
  • https://www.ansible.com/blog/ansible-best-practices-essentials
  • https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html

Git Guidelines

• Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR
• Follow the guidelines of writing a good commit message as described here https://chris.beams.io/posts/git-commit/ and summarized in the next few points:
  • In the subject line, use the present tense ("Add feature" not "Added feature").
  • In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
  • Limit the subject line to 72 characters or less.
  • Reference issues and pull requests liberally after the subject line.
  • Add more detailed description in the body of the git message (git commit -a to give you more space and time in your text editor to write a good message instead of git commit -am).