Sync to camunda-modeler@3.3.2

.github/CONTRIBUTING.md

@@ -0,0 +1,80 @@
+# How to Contribute
+
+Great to see you! Help us out by [filing bugs or feature requests](#working-with-issues), assisting others in our [forums](https://forum.zeebe.io/c/zeebe-modeler) or by [contributing improvements](#contributing-improvements).
+
+
+## Table of Contents
+
+* [Working with Issues](#working-with-issues)
+    * [Helping out](#helping-out)
+* [Contributing Improvements](#contributing-improvements)
+    * [Setting up the Project](#setting-up-the-project)
+    * [Discussing Code Changes](#discussing-code-changes)
+    * [Creating a Pull Request](#creating-a-pull-request)
+
+
+## Working with Issues
+
+We use our [issue tracker](https://github.com/zeebe-io/zeebe-modeler/issues) for project communication, discussion and planning.
+
+
+### Helping out
+
+* Share your perspective on issues
+* Be helpful and respect others when commenting
+
+
+## Contributing Improvements
+
+Learn how to setup the project locally, make changes and contribute bug fixes and new features through pull requests.
+
+### Setting up the Project
+
+The project consists of two subpackages: the client and the app. Test suites for both of them can be run separately.
+
+```plain
+git clone git@github.com:zeebe-io/zeebe-modeler.git
+cd zeebe-modeler && npm i
+
+// Run the test suite for both packages sequentially
+npm test
+
+// Run in dev mode
+npm start
+
+// Run tests, linter and build distro
+npm run all
+```
+
+### Discussing Code Changes
+
+Create a [pull request](#creating-a-pull-request) if you would like to have an in-depth discussion about some piece of code.
+
+
+### Code Style
+
+In addition to our automatically enforced [lint rules](https://github.com/bpmn-io/eslint-plugin-bpmn-io), please adhere to the following conventions:
+
+* Use modules for client (`import` / `export (default)`)
+* Use CommonJS for app (`require` / `module.exports`)
+
+### Creating a Pull Request
+
+We use pull requests for feature additions and bug fixes. If you are not yet familiar on how to create a pull request, [read this great guide](https://gun.io/blog/how-to-github-fork-branch-and-pull-request).
+
+Some things that make it easier for us to accept your pull requests
+
+* The code adheres to our conventions
+    * spaces instead of tabs
+    * single-quotes
+    * ...
+* The code is tested
+* The `npm run all` build passes (executes tests + linting)
+* The work is combined into a single commit
+* The commit messages adhere to the [conventional commits guidelines](https://www.conventionalcommits.org)
+
+
+We'd be glad to assist you if you do not get these things right in the first place.
+
+
+:heart: from the bpmn.io team.

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -17,25 +17,21 @@ Please provide the relevant context:
 
 __Describe the Bug__
 
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is. -->
 
 
 __Steps to Reproduce__
 
-Steps to reproduce the behavior:
-
 1. do this
 2. do that
 
 
 __Expected Behavior__
 
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what you expected to happen. -->
 
 
 __Environment__
 
-Please complete the following information:
-
  - OS: [e.g. MacOS 10.2, Windows 10]
  - Zeeber Modeler Version: [e.g. 0.5.0]

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,6 +6,6 @@ Please make sure you provide the relevant context.
 
 -->
 
-__Which issue does this PR address?_
+__Which issue does this PR address?__
 
-Closes #
+Closes #