Add SPDX identifier check to GHA #76
Merged
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
Signed-off-by: Sebastian Schildt <sebastian.schildt@de.bosch.com>
|
@SebastianSchildt Does the Github Actions also check for SPDX identifiers in README files, Config files for Zephyr etc.? |
nayakned
approved these changes
Jan 27, 2025
|
The action only tries to check "source files", so Readmes / .mds are exempted. It will only complain about "Non-compliant" files once they are touched by somebody again. So it enforces you to get better over time, without enforcing a "big bang" change. |
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.
This should make sure, that newly added or modified files in a PR have the correct SPDX license idenitifer