Skip to content

Latest commit

 

History

History
51 lines (33 loc) · 1.54 KB

CONTRIBUTING.md

File metadata and controls

51 lines (33 loc) · 1.54 KB

Contribution Guidelines

Tests

  • Pull requests that add any additional functionality should have tests which cover the new feature to ensure it does what is expected
  • Pull requests with failing tests will not be merged

Features

  • Keep feature based PRs as small as possible, with as few commits as necessary. These are easier to review and will be merged quicker

Bug Fixes

  • Make sure you reference the issue you're closing with Fixes #<issue number>

Commits

  • Squash/rebase any commits where possible to reduce the noise in the PR

Git commits

Reference the issue number, in the format (GH-###).

(GH-2) Add feature foo

Versions

This module supports Sensu v1

Branches

master

The master branch is for development against Sensu Classic.

Release process

  1. Update version in metadata.json
  2. Update CHANGELOG.md with the following command replacing --future-release with appropriate value. github_changelog_generator -u sensu -p puppet-module-sensuclassic --exclude-labels skip-changelog --future-release v3.2.0
  3. Update REFERENCE.md with the command bundle exec rake reference
  4. Commit changes and push to master
  5. Tag the new version, such as git tag -a 'v2.0.0' -m 'v2.0.0'
  6. Push tags git push --tags
  7. Update the puppet strings documentation with bundle exec rake strings:gh_pages:update
  8. Clean up tests with bundle exec rake spec_clean
  9. Remove junit directory from beaker runs rm -fr junit
  10. Build module with puppet module build
  11. Upload module to Puppet Forge.