Customizable copyright string check #103
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mbeacom
force-pushed
the
feat-custom-license-check
branch
3 times, most recently
from
cbce8ad
to
6b3df82
Compare
mbeacom
force-pushed
the
feat-custom-license-check
branch
from
6b3df82
to
2bc243c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to allow users to provide a custom copyright string. The copyright string can be used in conjunction with a custom template to ensure duplicate copyright headers are not created when the copyright string doesn't match the pre-defined collection:
copyright,mozilla public, orspdx-license-identifier.EDIT: Any guidance here is appreciated, if someone can spare it. Is there anything else I should plan to do for this PR? @willnorris
Fixes #56