ci: add compliance script checks to example repo - #101
Conversation
f750b68 to
bfaded7
Compare
There was a problem hiding this comment.
Compliance checks are failing due to extra newlines in this file, but I'm not sure if we want to strip those? I assume this license file was pulled directly from apache.org
There was a problem hiding this comment.
IMHO better not to strip. Messing with the defaults of what REUSE fetches will cause extra work when doing FOSS compliance.
Also, having an example on how to create an exception would be valuable too.
bfaded7 to
872fa10
Compare
|
Retriggered CI. |
There was a problem hiding this comment.
Do we need the upstream excludes files? I don't think so?
There was a problem hiding this comment.
Ah yeah, probably not. I guess we only need the rules file from upstream. I'll drop this
|
ci is complaining for the license file, vaguely remember someone else bumping into this and saying we should force it rather than adding the missing eof \n because something somewhere may checksum the license file or something, @kartben was it you? am I making stuff up? |
For what it's worth, the file hosted at https://www.apache.org/licenses/LICENSE-2.0.txt has a newline at the end- the file in this PR was copied from Zephyr. Do we know why there is a difference? It seems like we should be following the format of the file hosted by the Apache org |
872fa10 to
5a0a695
Compare
Add configuration files for linters used by Zephyr compliance checks. These files are duplicated from the Zephyr repo. Signed-off-by: Daniel DeGrasse <daniel.degrasse@analog.com>
Format example_west_command to comply with ruff CI checks Signed-off-by: Daniel DeGrasse <daniel.degrasse@analog.com>
Add support for running compliance checks on code contributed to the example repository, as a demonstration for how to implement custom compliance checks on top of those Zephyr provides Signed-off-by: Daniel DeGrasse <daniel.degrasse@analog.com>
5a0a695 to
9988878
Compare
5 participants
Add CI job to run compliance script checks within the example repo, as a demonstration of how to utilize and build on Zephyr's compliance checks.
This also enforces the compliance checks on this repo, so we need to reformat a few of the python scripts to comply with them