docs: adding contributing documentation (#35)

Author: Frnd-me

.github/pull_request_template.md

@@ -0,0 +1,46 @@
+# Pull Request
+
+<!--
+Please make sure to have read the CONTRIBUTING.md guidelines.
+-->
+
+## Description
+
+<!--
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+
+Fixes # (issue)
+-->
+
+## Type of change
+
+<!--
+Please delete options that are not relevant.
+-->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+
+## How Has This Been Tested?
+
+<!--
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+-->
+
+- [ ] Test A
+- [ ] Test B
+
+<!--
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
+-->

CONTRIBUTING.md

@@ -1,5 +1,16 @@
 # Contribution Guidelines
 
+For contributing, please refer to the guidelines below.
+
+## Development Setup
+
+We highly recommend using IntelliJ IDEA for development. Opening the project in IntelliJ IDEA will automatically configure the project for
+development.
+
+Additionally, we highly recommend using the [Pkl IntellJ Plugin](https://pkl-lang.org/intellij/current/index.html) to provide syntax
+highlighting and general support for Pkl files. Using this plugin, the provided CSML Pkl unit tests will automatically correctly import
+the CSM package provided by the project.
+
 ## Code Style
 
 This project uses the opinionated Prettier code formatter. The [Prettier Java](https://github.com/jhipster/prettier-java) plugin is used to format Java code. The Prettier 
@@ -15,4 +26,14 @@ npm install prettier-plugin-kotlin --save-dev
 
 Subsequently, IntelliJ IDEA can be configurated to use Prettier for formatting Java and Kotlin files. For this, you can use the 
 [File Watchers](https://plugins.jetbrains.com/plugin/7177-file-watchers) plugin inside IntelliJ IDEA. After installing the plugin, you can add a new file watcher for Prettier or import the
-provided `watchers.xml` file. File Watchers can be configured to run on save inside the _Tools → Actions on Save_ menu.
+provided `watchers.xml` file. File Watchers can be configured to run on save inside the _Tools → Actions on Save_ menu.
+
+## Pull Requests
+
+We accept pull requests for bug fixes and new features from forks. Please make sure to add unit tests for your changes. The CI will
+automatically build and test your changes.
+
+Make sure that your both the commits in your pull request and the pull request title are formatted according to the
+[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. Commit linting is enforced by the CI. Squashed commits
+upon merging are also enforced by the CI and will receive the pull request title as the commit message. We use Conventional Commits to
+generate the changelogs.