Skip to content

Commit 26fb8f2

Browse files
Update contibuter docs to mention that DCO signoff is mandatory (#202)
Signed-off-by: Abhilash Shetty <[email protected]>
1 parent 098a38e commit 26fb8f2

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,12 @@ LVM-LocalPV is an Apache 2.0 Licensed project and all your commits should be sig
3333
- DCO Signed
3434
* If your PR is not getting reviewed or you need a specific person to review it, please reach out to the OpenEBS Contributors. See [OpenEBS Community](https://github.com/openebs/openebs/tree/HEAD/community)
3535

36+
---
3637
## Sign your work
3738

3839
We use the Developer Certificate of Origin (DCO) as an additional safeguard for the OpenEBS projects. This is a well established and widely used mechanism to assure that contributors have confirmed their right to license their contribution under the project's license. Please read [dcofile](https://github.com/openebs/openebs/blob/HEAD/contribute/developer-certificate-of-origin). If you can certify it, then just add a line to every git commit message:
3940

41+
Please certify it by just adding a line to every git commit message. Any PR with Commits which does not have DCO Signoff will not be accepted:
4042
````
4143
Signed-off-by: Random J Developer <[email protected]>
4244
````
@@ -46,6 +48,8 @@ If you set your `user.name` and `user.email` in git config, you can sign your co
4648

4749
You can also use git [aliases](https://git-scm.com/book/tr/v2/Git-Basics-Git-Aliases) like `git config --global alias.ci 'commit -s'`. Now you can commit with `git ci` and the commit will be signed.
4850

51+
---
52+
4953
## Adding a changelog
5054
If PR is about adding a new feature or bug fix then the Author of the PR is expected to add a changelog file with their pull request. This changelog file should be a new file created under the `changelogs/unreleased` folder. Name of this file must be in `pr_number-username` format and contents of the file should be the one-liner text which explains the feature or bug fix.
5155

0 commit comments

Comments
 (0)