I noticed that the travis deploy setup was not properly picking up the cookbook name so I set it explicitly.
Added and updated some other misc stuff in the metadata to match reality (for example the LICENSE in repo was MIT but the attribute in metadata said all rights reserved), chef version support, issue url, source code url, etc.
[x] Update Changelog following the conventions laid out on Keep A Changelog
[x] Update README with any necessary configuration snippets
[x] RuboCop passes
[x] Existing tests pass
Purpose
Minor housekeeping
Known Compatibility Issues
actually enforces versions we actually support this should help users know what versions they can use and have code enforce it rather than expecting that they will actually review the README.md.
majormoses
commented
5 years ago
I noticed that the travis deploy setup was not properly picking up the cookbook name so I set it explicitly.
Added and updated some other misc stuff in the metadata to match reality (for example the LICENSE in repo was MIT but the attribute in metadata said all rights reserved), chef version support, issue url, source code url, etc.
Signed-off-by: Ben Abrams me@benabrams.it
Pull Request Checklist
https://travis-ci.org/Netuitive/chef-netuitive/jobs/505025901#L1176 motivated me and I noticed some other small nitpicks that I wanted to cleanup/fix.
General
[x] Update Changelog following the conventions laid out on Keep A Changelog
[x] Update README with any necessary configuration snippets
[x] RuboCop passes
[x] Existing tests pass
Purpose
Minor housekeeping
Known Compatibility Issues
actually enforces versions we actually support this should help users know what versions they can use and have code enforce it rather than expecting that they will actually review the
README.md.