Skip to content

Latest commit

 

History

History
44 lines (29 loc) · 2.51 KB

CONTRIBUTING.md

File metadata and controls

44 lines (29 loc) · 2.51 KB

Hello Contributors

Thx for your interest! We're so glad you're here.

Important Resources

Code of Conduct

Available via https://github.com/equinix/terraform-provider-equinix/blob/main/.github/CODE_OF_CONDUCT.md

Environment Details

https://github.com/equinix/terraform-provider-equinix/blob/main/GNUmakefile

How to Submit Change Requests

Please submit change requests and / or features via Issues. There's no guarantee it'll be changed, but you never know until you try. We'll try to add comments as soon as possible, though.

Pull Requests

All resource and data source changes must be reflected in the documentation, including new attributes and changes to existing attributes. The documentation is generated via make docs. For more detailed instructions for updating docs, see "Documenting the provider" in the development guide.

Titles For Pull Requests

We require pull request titles to follow the Conventional Commits specification

Before submitting the PR, please begin your title with one of these available types below:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

How to Report a Bug

Bugs are problems in code, in the functionality of an application or in its UI design; you can submit them through Issues as well.