feat: initialize repository

.editorconfig

@@ -0,0 +1,15 @@
+# Editor configuration, see http://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.xml]
+indent_size = 4
+
+[*.md]
+max_line_length = off
+trim_trailing_whitespace = false

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @MarcScheib

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,238 @@
+# Contributing
+
+We'd love for you to contribute and to make this project even better than it is today!
+Here are the guidelines we'd like you to follow:
+
+- [Question or Problem?](#question)
+- [Issues and Bugs](#issue)
+- [Feature Requests](#feature)
+- [Docs Improvements](#docs)
+- [Submission Guidelines](#submit)
+- [Coding Rules](#rules)
+- [Commit Message Guidelines](#commit)
+
+## <a name="question"></a> Got a Question or Problem?
+
+If you have questions about how to use our plugins, please direct these to the respective repository issues
+or [StackOverflow][stackoverflow].
+
+## <a name="issue"></a> Found an Issue?
+
+If you find a bug in the source code or a mistake in the documentation, you can help us by
+submitting an issue to our [GitHub Repository][github]. Even better you can submit a Pull Request
+with a fix.
+
+**Please see the Submission Guidelines below**.
+
+## <a name="feature"></a> Want a Feature?
+
+You can request a new feature by submitting an issue to our [GitHub Repository][github]. If you
+would like to implement a new feature then consider what kind of change it is:
+
+- **Major Changes** that you wish to contribute to the project should be discussed first
+ so that we can better coordinate our efforts, prevent duplication of work, and help you to
+ craft the change so that it is successfully accepted into the project.
+- **Small Changes** can be crafted and submitted to the [GitHub Repository][github] as a Pull Request.
+
+## <a name="docs"></a> Want a Doc Fix?
+
+If you want to help improve the docs, it's a good idea to let others know what you're working on to
+minimize duplication of effort. Before starting, check out the open issues.
+Comment on an issue to let others know what you're working on, or create a new issue if your work
+doesn't fit within the scope of any of the existing doc fix projects.
+
+For large fixes, please build and test the documentation before submitting the Pull Request to be
+sure you haven't accidentally introduced any layout or formatting issues. You should also make
+sure that your commit message is labeled "docs:" and follows the **Git Commit Guidelines** outlined below.
+
+## <a name="submit"></a> Submission Guidelines
+
+### Submitting an Issue
+
+Before you submit your issue search the archive, maybe your question was already answered.
+
+If your issue appears to be a bug, and hasn't been reported, open a new issue.
+Help us to maximize the effort we can spend fixing issues and adding new
+features, by not reporting duplicate issues. Providing the following information will
+increase the chances of your issue being dealt with quickly:
+
+- **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
+- **Motivation for or Use Case** - explain why this is a bug for you
+- **Version(s)** - is it a regression?
+- **Browsers and Operating System** - is this a problem with all browsers or only IE8?
+- **Reproduce the Error** - provide a live example (using Plunker or
+ JSFiddle) or an unambiguous set of steps.
+- **Related Issues** - has a similar issue been reported before?
+- **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
+ causing the problem (line of code or commit)
+
+### Submitting a Pull Request
+
+Before you submit your pull request consider the following guidelines:
+
+- Search the repository for an open or closed Pull Request
+ that relates to your submission. You don't want to duplicate effort.
+- Make your changes in a new git branch:
+
+ ```shell
+ git checkout -b my-fix-branch main
+ ```
+
+- Create your patch, **including appropriate test cases**.
+- Follow our [Coding Rules](#rules).
+- Commit your changes using a descriptive commit message that follows our
+ [commit message conventions](#commit-message-format). Adherence to
+ the [commit message conventions](#commit-message-format)
+ is required because release notes are automatically generated from these messages.
+
+ ```shell
+ git commit -a
+ ```
+
+ Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
+
+- Build your changes locally to ensure all the tests pass:
+
+ ```shell
+ gulp test
+ ```
+
+- Push your branch to GitHub:
+
+ ```shell
+ git push origin my-fix-branch
+ ```
+
+- In GitHub, send a pull request to the `main` branch.
+- If we suggest changes then:
+ - Make the required updates.
+ - Commit your changes to your branch (e.g. `my-fix-branch`).
+ - Push the changes to your GitHub repository (this will update your Pull Request).
+
+If the PR gets too outdated we may ask you to rebase and force push to update the PR:
+
+```shell
+git rebase main -i
+git push origin my-fix-branch -f
+```
+
+_WARNING. Squashing or reverting commits and forced push thereafter may remove GitHub comments
+on code that were previously made by you and others in your commits._
+
+#### After your pull request is merged
+
+After your pull request is merged, you can safely delete your branch and pull the changes
+from the main (upstream) repository:
+
+- Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
+
+ ```shell
+ git push origin --delete my-fix-branch
+ ```
+
+- Check out the main branch:
+
+ ```shell
+ git checkout main -f
+ ```
+
+- Delete the local branch:
+
+ ```shell
+ git branch -D my-fix-branch
+ ```
+
+- Update your main with the latest upstream version:
+
+ ```shell
+ git pull --ff upstream main
+ ```
+
+## <a name="rules"></a> Coding Rules
+
+To ensure consistency throughout the source code, keep these rules in mind as you are working:
+
+- All features or bug fixes **must be tested** by one or more specs.
+- All public API methods **must be documented**.
+- Code should be check against our **lint rules**: `gulp lint`.
+
+## <a name="commit"></a> Git Commit Guidelines
+
+We have very precise rules over how our git commit messages can be formatted. This leads to **more
+readable messages** that are easy to follow when looking through the **project history**. But also,
+we use the git commit messages to **generate the change logs**.
+
+The commit message formatting can be added using a typical git workflow
+or through the use of a CLI wizard ([Commitizen](https:/commitizen/cz-cli)).
+To use the wizard, run `npm run commit` in your terminal after staging your changes in git.
+
+### Commit Message Format
+
+Each commit message consists of a **header** and a **body**. The header has a special
+format that includes a **type**, a **scope**, and a **subject**:
+
+```
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+---
+<BLANK LINE>
+<diff>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+The header line cannot be longer than 50 characters, any other line
+cannot be longer than 72 characters! This allows
+the message to be easier to read on GitHub as well as in various git tools.
+
+### Revert
+
+If the commit reverts a previous commit, it should begin with `revert:`,
+followed by the header of the reverted commit. In the body it should
+say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
+
+### Type
+
+Must be one of the following:
+
+- **feat**: A new feature
+- **fix**: A bug fix
+- **docs**: Documentation only changes
+- **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
+ semi-colons, etc)
+- **refactor**: A code change that neither fixes a bug nor adds a feature
+- **perf**: A code change that improves performance
+- **test**: Adding missing tests
+- **chore**: Changes to the build process or auxiliary tools and libraries such as documentation
+ generation
+
+### Scope
+
+The scope could be anything specifying place of the commit change.
+
+### Subject
+
+The subject contains succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize first letter
+- no dot (.) at the end
+
+### Body
+
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.
+
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines.
+The rest of the commit message is then used for this.
+
+### Diff
+
+Add the diff of the commit from `git diff HEAD --stat=73`
+A git diff from a sub directory is possible with the parameter `--relative`.
+Filter can be used via `--diff-filter=[(A|C|D|M|R|T|U|X|B)…​[*]]`.
+
+[github]: https:/MarcScheib/eam-js
+[stackoverflow]: http://stackoverflow.com/

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/workflows/pull-request_cache-cleanup.yml

@@ -0,0 +1,12 @@
+name: Backend - Pull Request - Cleanup action caches
+
+on:
+ pull_request:
+ types:
+ - closed
+ workflow_dispatch:
+
+jobs:
+ cleanup:
+ name: Cleanup
+ uses: CycriLabs/eam-gha-workflows/.github/workflows/be-fe_pull-request_cache-cleanup.yml@main

.github/workflows/pull-request_test-build.yml

@@ -0,0 +1,16 @@
+name: Backend - Pull Request - Test
+
+on:
+ pull_request:
+
+concurrency:
+ group: build-${{ github.head_ref || github.ref_name }}
+ cancel-in-progress: true
+
+jobs:
+ test-and-build:
+ name: Test and build
+ uses: CycriLabs/eam-gha-workflows/.github/workflows/be_pull-request_test-build.yml@main
+ secrets: inherit
+ with:
+ java-version: 17