Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gemspec: add license metadata #229

Merged
merged 1 commit into from
Feb 13, 2021
Merged

gemspec: add license metadata #229

merged 1 commit into from
Feb 13, 2021

Conversation

priv-kweihmann
Copy link
Contributor

Description

so the data is visible on e.g. rubygems.org and can be used by compliance tooling.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

Unchecked box do not apply IMO, as this is a non-functional change

so the data is visible on e.g. rubygems.org and can be used
by compliance tooling

Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
@tas50
Copy link
Contributor

tas50 commented Feb 13, 2021

I don't know how we missed that bit. Thanks

@tas50
Copy link
Contributor

tas50 commented Feb 13, 2021

@priv-kweihmann I added a new test in our linter to make sure all our gemspecs have a license defined: chef/chefstyle#127

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants