Open
Conversation
Signed-off-by: Christian Decker <christian.decker@homag.com>
chrisdecker1201
force-pushed
the
feature/pre-commit
branch
from
b80b029 to
2d9e69a
Compare
Member
sorry, that no discussion happened yet. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a PR for discussion :).
I was looking for a possibility to introduce some kind of automatically validation of SPDX files inside of a git repository.
I found
pre-commit, which could be a solution for my goal. It will execute thepyspdxtools --infilefor validation.Currenty this is working only for one file and only for *.json and not the other possible file-formats, but it's working.
Do you have interest in integrating
pre-commit? If so, I think I will try to make this possibel.