Add copyright 2026 headers for source code#22
Conversation
|
LGTM, maybe we should add a PR check to ensure that the header is present in all new/updated files, that will prevent this reoccurring, I think we have one in hyperlight. |
simongdavies
left a comment
There was a problem hiding this comment.
The only question I have is about teh c stubds, maybe @jprendes knows the origin of those
https://github.com/hyperlight-dev/hyperlight/blob/main/dev/check-license-headers.sh 2026 is correct for this since they just got released |
aec9e1d to
5f78422
Compare
The stubs are ours, except for the I realise we should aknowledge that somewhere, or rewrite it without basing it on musl. I think the right thing to do is to split |
|
I'll rewrite all the stubs in rust, I propose you go ahead as it is, as the concern with the stub will be sorted with the rewrite |
Signed-off-by: Doru Blânzeanu <dblnz@pm.me>
- Also reorder CI jobs alphabetically Signed-off-by: Doru Blânzeanu <dblnz@pm.me>
5f78422 to
5624ac3
Compare
I've updated to remove the stub file containing the musl function |
Description
This PR adds copyright headers for
hyperlight-jssource codeA couple of remarks: