-
Notifications
You must be signed in to change notification settings - Fork 162
Initial version of pre-commit "Check SPDX-License-Identifier" #625
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
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Let's exclude the following files:
|
All done. This is a full cleanup now:
Could you please do a full review? After this PR is approved I will:
|
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.
Thanks a lot for the cleanup, Ralf!
As the last step, I removed the EULA paragraphs, thinking that they are obsolete after adding the SPDX-License-Identifier lines.
Yes, I agree this makes it cleaner. The two lines (copyright & SPDX license identifier) are enough.
/ok to test 85e0182 |
This comment has been minimized.
This comment has been minimized.
If we're doing a big cleanup here, we should also move the copyright statements to use SPDX copyright statements instead. I.e. |
Sounds good. I could try to squeeze that in later (another weekend). I wouldn't know what exactly to do though. Could you please describe the exact requirements in an issue? |
Might be worth trying this pre-commit hook as well: https://github.com/espressif/check-copyright It looks to have the ability to automatically update files that don't meet the check as well? |
We have the unusual situation that we have to backport to the code generators (in two different repos), which is probably 99% of the manual work, as it stands. I want to propose to take one step at a time.
|
This comment was marked as off-topic.
This comment was marked as off-topic.
/ok to test 9c54b37 |
@leofang Assuming testing here passes as expected, this PR and the cython-gen update are ready for merging. |
Forgot to add: no changes needed for cybind |
I am not sure I follow -- what's this for? |
Oops sorry I was jumping between PRs. Please ignore!
(This was for pybind11)
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Leo Fang ***@***.***>
Sent: Tuesday, May 13, 2025 6:30:26 PM
To: NVIDIA/cuda-python ***@***.***>
Cc: Ralf Grosse Kunstleve ***@***.***>; Assign ***@***.***>
Subject: Re: [NVIDIA/cuda-python] Initial version of pre-commit "Check SPDX-License-Identifier" (PR #625)
[https://avatars.githubusercontent.com/u/5534781?s=20&v=4]leofang left a comment (NVIDIA/cuda-python#625)<#625 (comment)>
Everything as before, but using -DCMAKE_BUILD_TYPE=MinSizeRel, I'm also getting the double free or corruption error.
I am not sure I follow -- what's this for?
—
Reply to this email directly, view it on GitHub<#625 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAFUZACJTFTGSPM34H6KXJ326KMDFAVCNFSM6AAAAAB46Q46ECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZYGM3TAMJRHE>.
You are receiving this because you were assigned.Message ID: ***@***.***>
|
/ok to test 33f5a49 |
I didn't trigger the CI because the only file changed since the last full run is The codegen PR is in sync, and I ran the codegen for all modules ( |
|
Description
Closes #586
Minimalistic implementation:
toolshed/check_spdx.py
New
.spdx-ignore
: enumerates all files that do not containSPDX-License-Identifier: