[plc4x-website] branch asf-site updated: Site checkin for project PLC4X: Jenkins Tools

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new b69ac46cd Site checkin for project PLC4X: Jenkins Tools
b69ac46cd is described below

commit b69ac46cd99466962eb121c693e26418a065ae21
Author: jenkins <bui...@apache.org>
AuthorDate: Sat Oct 21 22:59:18 2023 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 developers/contributing.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/developers/contributing.html b/developers/contributing.html
index 833aa99b6..06bd5f4d5 100644
--- a/developers/contributing.html
+++ b/developers/contributing.html
@@ -273,6 +273,14 @@
 </div>
 </div>
 <div class="sect2">
+<h3 id="commits">Commits</h3>
+<div class="paragraph">
+<p>We make use of <a 
href="https://www.conventionalcommits.org/en/v1.0.0/";>conventional commits</a>.
+As plc4x is a monolithic polyglot repository we usually define the scope as 
<code>&#8230;&#8203;(plc4[language shortcut here]/subcomponent)</code>
+(e.g. a new feature in Bacnet in the Golang part would have a message of 
<code>feat(plc4go/bacnet): cool new feature for&#8230;&#8203;</code>).</p>
+</div>
+</div>
+<div class="sect2">
 <h3 id="pull_requests">Pull-Requests</h3>
 <div class="paragraph">
 <p>The simplest way to submit code changes, is via a GitHub pull-request.</p>