From 8a9035125207dd46d1d530d8797543d58dfbf01d Mon Sep 17 00:00:00 2001
From: dkorpos <dkorpos@emarsys.com>
Date: Fri, 21 Jun 2024 11:11:09 +0200
Subject: [PATCH] feat(contribution): create contribution guideline
 (CONTRIBUTING.md)

---
 CONTRIBUTING.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 CONTRIBUTING.md

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..fa26567
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,14 @@
+# Contribution guideline
+
+## Create a GitHub Pull Request
+
+### 1. Fork the repository
+### 2. Make changes, commit them to your fork
+ - As the release process is automated, write your commit message according to the [semantic-release documentation](https://github.com/semantic-release/semantic-release?tab=readme-ov-file#commit-message-format)'s default config
+### 3. Push your changes to your fork
+### 4. Create a pull request
+ - Go to https://github.com/emartech/escher-suiteapi-js/compare
+ - Select your fork and branch as head
+ - Select emartech/escher-suiteapi-js and master as base
+### 5. The code has to be approved and merged by a maintainer
+ - Ask the @js-maintainers user group on Slack for review
\ No newline at end of file