Skip to content

Latest commit

 

History

History
39 lines (27 loc) · 1.77 KB

File metadata and controls

39 lines (27 loc) · 1.77 KB

Contributing Guidelines

Contributor roles

Open source should not be just about writing code. A good open source project also needs:

  • Documentation writers
  • Testers
  • Tutorial writers
  • Evangelists
  • Automation builders

If you want to get involved in a role (including ones we may have missed!) reach out to one of the committers.

Working on issues

  • Ensure there is a GitHub issue for any bug before submitting a PR.
  • Enhancements should be discussed and a feature request issue created, before starting work on it.
  • Fork and raise a PR for work.
  • Add tests for any enhancements.
  • Ensure documentation is updated accordingly, including adding unit test reports.
  • Ensure API docs are updated (speak to an HCL-ite if required).
  • Ensure changelog is updated.

Development Environment

Pushing unit tests to documentation

In a Terminal, navigate to the directory containing the unit-tests-to-docs.sh file. Run the file, passing two parameters - a string matching part of the filename for the tests and a new folder name to push the results to. For example, ./unit-tests-to-docs.sh TestCol* TestCollections

## PRs

  • When ready, complete a PR and submit.
  • Review the requirements for submitting a PR, for example writing test and updating documentation.