@@ -6,14 +6,14 @@ email, or any other method with the owners of this repository before making a ch
66Please note we have a code of conduct, please follow it in all your interactions with the project.
77
88## Pull Request Process
9-
10- 1 . Ensure any install or build dependencies are removed before the end of the layer when doing a
9+ 1 . Ensure you signed all your commits with Developer Certificate of Origin (DCO).
10+ 2 . Ensure any install or build dependencies are removed before the end of the layer when doing a
1111 build.
12- 2 . Update the README.md with details of changes to the interface, this includes new environment
12+ 3 . Update the README.md with details of changes to the interface, this includes new environment
1313 variables, exposed ports, useful file locations and container parameters.
14- 3 . Increase the version numbers in any examples files and the README.md to the new version that this
14+ 4 . Increase the version numbers in any examples files and the README.md to the new version that this
1515 Pull Request would represent. The versioning scheme we use is [ SemVer] ( http://semver.org/ ) .
16- 4 . You may merge the Pull Request in once you have the sign-off of two other developers, or if you
16+ 5 . You may merge the Pull Request in once you have the sign-off of two other developers, or if you
1717 do not have permission to do that, you may request the second reviewer to merge it for you.
1818
1919## Contributor Code of Conduct
@@ -52,3 +52,22 @@ issue or contacting one or more of the project maintainers.
5252This Code of Conduct is adapted from the [ Contributor Covenant] ( http://contributor-covenant.org ) ,
5353version 1.2.0, available at
5454[ http://contributor-covenant.org/version/1/2/0/ ] ( http://contributor-covenant.org/version/1/2/0/ )
55+
56+ ### Sign your work
57+
58+ We use the Developer Certificate of Origin (DCO) as a additional safeguard
59+ for the HackMD project. This is a well established and widely used
60+ mechanism to assure contributors have confirmed their right to license
61+ their contribution under the project's license.
62+ Please read [ contribute/developer-certificate-of-origin] [ dcofile ] .
63+ If you can certify it, then just add a line to every git commit message:
64+
65+ ````
66+ Signed-off-by: Random J Developer <[email protected] > 67+ ````
68+
69+ Use your real name (sorry, no pseudonyms or anonymous contributions).
70+ If you set your ` user.name ` and ` user.email ` git configs, you can sign your
71+ commit automatically with ` git commit -s ` . You can also use git [ aliases] ( https://git-scm.com/book/tr/v2/Git-Basics-Git-Aliases )
72+ like ` git config --global alias.ci 'commit -s' ` . Now you can commit with
73+ ` git ci ` and the commit will be signed.
0 commit comments