Name: dco
Owner: Probot
Description: GitHub App that enforces the Developer Certificate of Origin (DCO) on Pull Requests
Created: 2017-03-25 13:38:14.0
Updated: 2018-05-20 21:51:38.0
Pushed: 2018-05-19 13:35:15.0
Homepage: https://github.com/apps/dco
Size: 158
Language: JavaScript
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
a GitHub Integration built with probot that enforces the Developer Certificate of Origin (DCO) on Pull Requests. It requires all commit messages to contain the Signed-off-by line with an email address that matches the commit author.
Configure the integration for your organization or repositories. Enable required status checks if you want to enforce the DCO on all commits.
See docs/deploy.md if you would like to run your own instance of this plugin.
It is possible to disable the check for commits authored and signed by members of the organization the repository belongs to. To do this, place the following configuration file in .github/dco.yml on the default branch:
ire:
mbers: false
When this setting is present on a repository that belongs to a GitHub user (instead of an organization), only the repository owner is allowed to push commits without sign-off.
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, reformatted for readability:
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.
Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.
is my commit message
ed-off-by: Random J Developer <random@developer.example.org>
Git even has a -s command line option to append this automatically to your commit message:
t commit -s -m 'This is my commit message'
Once installed, this integration will set the status to failed if commits in a Pull Request do not contain a valid Signed-off-by line.
If you want to learn more about the DCO and why it might be necessary, here are some good resources: