-
Notifications
You must be signed in to change notification settings - Fork 5
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
fix(license): remove license file #211
fix(license): remove license file #211
Conversation
This PR removes the license file and uses the license field in meta data instead as the single source of declaring a license for a plugin or a recipe. Resolves pollination#154
Pull Request Test Coverage Report for Build 411289470Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep the change makes sense. Reckon we can probably just drop anything to do with a file called LICENSE
😀
if license_string is not None: | ||
with open(os.path.join(folder_path, 'LICENSE'), 'w') as f: | ||
f.write(license_string) | ||
with open(os.path.join(folder_path, 'LICENSE'), 'w') as f: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just drop the LICENSE file if we're not actually going to write anything there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might still be helpful for user discovery. We can remove it at any point and it shouldn't break anything since it is only generated insider the folder when one uses to_folder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep the change makes sense. Reckon we can probably just drop anything to do with a file called LICENSE
😀 If you want to keep the file for some reason the you can still consider this PR approved!
🎉 This PR is included in version 1.21.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This PR removes the license file and uses the license field in meta data instead as the single source of declaring a license for a plugin or a recipe.
Resolves #154