The Developer Certificate of Origin (DCO) checks
This certifies that you are able to submit your contribution to our repository under the license of the repository, and for the contribution to be redistributed under that same license.
You can "sign" this certificate by including a line in the git commit of "
Signed-off-by: Legal Name <email-address>", using the email address associated with your GitHub account.
How to work with DCO
You need to ensure that every commit message has a line "
Signed-off-by: Your Legal Name <your-email@address>", and while you could add that manually every time, here are the steps to follow so the computer can add it for you:
- Set your legal name in the git configuration:
git config user.name "Legal Name"
- Set your email in the git configuration:
git config user.email "email@address"
- Add the
- Add a git alias:
git config --global alias.c 'commit --signoff'and then run "
git c" instead of "
- In IntelliJ
- Add a git alias:
The merge or a PR must also have a DCO so we can know the entire repository is under the associated license.
- When Merging a Pull Request through "squash and merge", include the
Signed-off-bylines from every contributor, and add one for you as the person merging.
When you have a DCO failure on your PR from DCO Bot
Click on that "Details" link and follow the instructions.
When you have a DCO failure on your PR from CI
On Circle CI you will see:
On Jenkins in the full Console Output you will see:
If this is only from CI and not from DCO Bot, then please contact a Maintainer, as it probably means that the
master branch has a commit that does not follow DCO which will necessitate a
Feel free to check out this tutorial for more help.
The sign off needs to be using your legal name, not a pseudonym. Git has a built-in mechanism to allow this with the
--signoff argument to
git commit command, providing your
user.email have been setup correctly.
If you have any questions, you can reach us on Besu chat.