[olang/patches/.build.yml] build success

[olang/patches/.build.yml] build success

[builds.sr.ht]

olang/patches/.build.yml: SUCCESS in 37s

[docs: add DCO information on hacking page][0] from [Johnny Richard][1]

[0]: https://lists.sr.ht/~johnnyrichard/olang-devel/patches/49746
[1]: mailto:johnny@johnnyrichard.com

✓ #1155599 SUCCESS olang/patches/.build.yml https://builds.sr.ht/~johnnyrichard/job/1155599

[PATCH olang] docs: add DCO information on hacking page

[Johnny Richard]

All contributions must be signed off by the author. There is a link to
the Developer Certificate of Origin version 1.1.

Signed-off-by: Johnny Richard <johnny@johnnyrichard.com>
---
I'm adding a link to the DCO document.  I'm not sure if this document
will survive for a long time.  Let me know if I should attach the DCO
text to our documentation.

 docs/pages/hacking.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/pages/hacking.md b/docs/pages/hacking.md
index 7ebd4b3..ef88791 100644
--- a/docs/pages/hacking.md
+++ b/docs/pages/hacking.md
@@ -68,7 +68,11 @@ make check
 Submitting a patch
 ------------------
 
-Before submit a patch, ensure your code follows our coding style and is
+All contributors are required to "sign-off" their commits (using git commit -s)
+to indicate that they have agreed to the [Developer Certificate of
+Origin](https://developercertificate.org/).
+
+Before submit the patch, ensure the code follows our coding style and is
 well-tested. After that, you\'re good to follow the steps bellow.
 
 ### Step 1: Commit your changes
-- 
2.43.2

Re: [PATCH olang] docs: add DCO information on hacking page

[Carlos Maniero]

LGTM! Although since I've no permission to trigger the pipeline I'll
leave it to you the merge.

Re: [PATCH olang] docs: add DCO information on hacking page

[Johnny Richard]

Thanks for reviewing it. Applied.

build: https://builds.sr.ht/~johnnyrichard/job/1157966

To git.sr.ht:~johnnyrichard/olang
   d12d495..0b69644  main -> main