From 89b581c6fa663d8a9db728d98e7f56c83c991444 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Tue, 11 Feb 2020 14:34:08 -0700 Subject: rework script into API::GitForge generic interface Signed-off-by: Sean Whitton --- CONTRIBUTING | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 CONTRIBUTING (limited to 'CONTRIBUTING') diff --git a/CONTRIBUTING b/CONTRIBUTING new file mode 100644 index 0000000..fbe48bf --- /dev/null +++ b/CONTRIBUTING @@ -0,0 +1,43 @@ +Submitting patches +================== + +Thank you for your interest in contributing to this project! + +Please **do not** submit a pull request on GitHub. The repository +there is an automated mirror, and I don't develop using GitHub's +platform. + +Instead, either + +- publish a branch somewhere (a GitHub fork is fine), and e-mail + asking me to merge your branch, possibly + using git-request-pull(1) + +- prepare patches with git-format-patch(1), and send them to + , probably using git-send-email(1) + +You may find useful. + +Reporting bugs +============== + +Please use the CPAN bug tracker: + + +Please read "How to Report Bugs Effectively" to ensure your bug report +constitutes a useful contribution to the project: + + +Signing off your commits +======================== + +Contributions are accepted upstream under the terms set out in the +file ``COPYING``. You must certify the contents of the file +``DEVELOPER-CERTIFICATE`` for your contribution. To do this, append a +``Signed-off-by`` line to end of your commit message. An easy way to +add this line is to pass the ``-s`` option to git-commit(1). Here is +an example of a ``Signed-off-by`` line: + +:: + + Signed-off-by: Sean Whitton -- cgit v1.2.3