You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add CI job to verify all Rust files have license headers (#512)
* Add script and CI job to check license headers in Rust files
Co-authored-by: simongdavies <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Add license headers to files that were missing them
Co-authored-by: simongdavies <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Add just target for checking license headers
Co-authored-by: simongdavies <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Fix Label Checker test and improve license header script
Co-authored-by: simongdavies <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Add license headers to files in src/hyperlight_guest_capi/
Co-authored-by: simongdavies <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Add license header to idtr.rs and fix imports
Co-authored-by: simongdavies <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Update README with DCO sign-off information
Signed-off-by: Simon Davies <[email protected]>
* Add documentation for DCO compliance
Signed-off-by: copilot-swe-agent[bot] <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Update documentation on GPG signing and DCO requirements
Signed-off-by: copilot-swe-agent[bot] <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Fix markdown linting issues in CONTRIBUTING.md and add markdownlint config
Co-authored-by: marosset <[email protected]>
Signed-off-by: Simon Davies <[email protected]>
* Address review feedback: update copyright year to 2025, simplify docs, use just in CI, remove markdownlint config
- Remove .markdownlint.json file as it wasn't being used
- Update copyright year from 2024 to 2025 in license header check script and all files with license headers
- Simplify docs/commit-signing.md to remove duplication and reference GitHub's documentation
- Update CONTRIBUTING.md to reference GitHub docs instead of duplicating GPG setup instructions
- Update CI workflow to use `just check-license-headers` for consistency
Co-authored-by: jsturtevant <[email protected]>
* Remove commit signing docs and simplify references per review feedback
- Remove docs/commit-signing.md file as requested
- Update CONTRIBUTING.md to point to GitHub's documentation instead
- Restore the credit comment in CONTRIBUTING.md
- Remove commit signing section from README.md
Signed-off-by: Copilot AI <[email protected]>
Co-authored-by: jsturtevant <[email protected]>
* Revert GH PR workflow to use ./dev/check-license-headers.sh
Cannot use the just command since just is not available on this runner
Signed-off-by: Simon Davies <[email protected]>
* Update copyright year to 2025 in all remaining Rust files
Complete the copyright year update that was started in commit 3ea4801 but only partially finished. This updates all remaining Rust files from "Copyright 2024" to "Copyright 2025" for consistency across the codebase.
Signed-off-by: Copilot AI <[email protected]>
Co-authored-by: simongdavies <[email protected]>
* Fix PR review issues: restore original files and update workflow
Co-authored-by: jsturtevant <[email protected]>
* Update ValidatePullRequest.yml to use script directly instead of just command
Co-authored-by: jsturtevant <[email protected]>
* Revert copyright year changes for files with existing license headers
Files that already had license headers should not have their copyright
years modified. This commit reverts all copyright year changes from
2025 back to 2024 for files that already had license headers, while
preserving the license headers that were legitimately added to files
that were completely missing them.
Signed-off-by: Copilot AI <[email protected]>
Co-authored-by: jsturtevant <[email protected]>
---------
Signed-off-by: Simon Davies <[email protected]>
Signed-off-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: simongdavies <[email protected]>
Co-authored-by: marosset <[email protected]>
Co-authored-by: jsturtevant <[email protected]>
Co-authored-by: Simon Davies <[email protected]>
Co-authored-by: James Sturtevant <[email protected]>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+38-7Lines changed: 38 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This project welcomes contributions. Most contributions require you to signoff o
4
4
the Developer Certificate of Origin (DCO). When you submit a pull request, a DCO-bot will automatically determine
5
5
whether you need to provide signoff for your commit. Please follow the instructions provided by DCO-bot, as pull
6
6
requests cannot be merged until the author(s) have provided signoff to fulfill the DCO requirement.
7
-
You may find more information on the DCO requirements [below](#developer-certificate-of-origin-signing-your-work).
7
+
You may find more information on the DCO requirements [below](#developer-certificate-of-origin-and-gpg-signing).
8
8
9
9
## Issues
10
10
@@ -31,20 +31,28 @@ All contributions come through pull requests. To submit a proposed change, we re
31
31
- Code changes require tests
32
32
- Make sure to run the linters to check and format the code
33
33
4. Update relevant documentation for the change
34
-
5. Commit with [DCO sign-off](#developer-certificate-of-origin-signing-your-work) and open a PR
34
+
5. Commit with [DCO sign-off](#developer-certificate-of-origin-and-gpg-signing) and open a PR
35
35
6. Wait for the CI process to finish and make sure all checks are green
36
36
7. A maintainer of the project will be assigned, and you can expect a review within a few days
37
37
38
38
#### Use work-in-progress PRs for early feedback
39
39
40
40
A good way to communicate before investing too much time is to create a "Work-in-progress" PR and share it with your reviewers. The standard way of doing this is to add a "[WIP]" prefix in your PR's title and open the pull request as a draft.
41
41
42
-
### Developer Certificate of Origin: Signing your work
42
+
### Developer Certificate of Origin and GPG Signing
43
43
44
44
#### Every commit needs to be signed
45
45
46
+
This project requires two types of signatures on all commits:
47
+
48
+
1.**Developer Certificate of Origin (DCO) Sign-off**: A text attestation that you have the right to submit the code
49
+
2.**GPG Signature**: A cryptographic signature verifying your identity
50
+
51
+
**For DCO Sign-offs:**
52
+
46
53
The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the [DCO](https://developercertificate.org/), reformatted for readability:
47
-
```
54
+
55
+
```text
48
56
By making a contribution to this project, I certify that:
49
57
50
58
(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
@@ -70,18 +78,41 @@ Git even has a `-s` command line option to append this automatically to your com
70
78
git commit -s -m 'This is my commit message'
71
79
```
72
80
73
-
Each Pull Request is checked whether or not commits in a Pull Request do contain a valid Signed-off-by line.
81
+
**For GPG Signatures:**
82
+
83
+
GPG signatures verify the identity of the committer. For detailed setup instructions, see GitHub's documentation on [signing commits](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
84
+
85
+
Quick setup:
74
86
75
-
#### I didn't sign my commit, now what?!
87
+
```sh
88
+
git config --global user.signingkey YOUR_KEY_ID
89
+
git config --global commit.gpgsign true
90
+
```
91
+
92
+
**For both DCO sign-off and GPG signature in one command:**
93
+
94
+
```sh
95
+
git commit -S -s -m 'This is my signed and signed-off commit message'
96
+
```
97
+
98
+
For detailed instructions on setting up GPG signing, see [GitHub's documentation on signing commits](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
99
+
100
+
Each Pull Request is checked to ensure all commits contain valid DCO sign-offs and GPG signatures.
101
+
102
+
#### I didn't sign my commit, now what?
76
103
77
104
No worries - You can easily replay your changes, sign them and force push them!
78
105
106
+
**For adding both DCO sign-off and GPG signature:**
For more detailed instructions on setting up GPG signing, see [GitHub's documentation on signing commits](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
0 commit comments