Buckets:
Contributing
Developer Certificate of Origin
The Developer Certificate of Origin (DCO) is a way to certify that you wrote or otherwise have the right to submit the code you are contributing to the project.
By signing off on your contribution, you certify the following DCO (Version 1.1):
- Full text of the DCO (https://developercertificate.org/):
Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (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 (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
Sign your work
To certify the DCO, you must add a "Signed-off-by" line to your commit messages.
Important: You must use your real name (no pseudonyms or anonymous contributions).
Example:
Fix typo in tokenizer config
Signed-off-by: Your Name <your@email.com>
Git Command
If you are using the command line, you can sign off automatically by adding the -s flag:
git commit -s -m "Your commit message"
Submitting changes
- Fork the repository on Hugging Face.
- Create a branch for your fix.
- Commit your changes with the
-sflag to sign them. - Open a Pull Request (PR) on the Community tab of the model page.
Xet Storage Details
- Size:
- 2.51 kB
- Xet hash:
- 401b41f0a7c798f073df43637758262f4bf306f916625b56daa2534a57c20661
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.