feat: initial commit

Author: me-marcel

.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/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.yml

@@ -0,0 +1,49 @@
+name: Pull request
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  lint_commit:
+    name: Lint commit
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: '20.9.0'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run commit lint
+        run: npx commitlint --from="$(git merge-base HEAD origin/${{ github.event.pull_request.base.ref }})"
+
+  check_code:
+    name: Check code
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: '8.2'
+          extensions: mbstring, curl
+
+      - name: Install Composer
+        run: |
+          curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer
+          composer install --ignore-platform-reqs --no-scripts
+
+      - name: Run Pint
+        run: vendor/bin/pint --test
+
+      - name: Run PHPStan
+        run: vendor/bin/phpstan analyse --memory-limit=2G

.github/workflows/release.yml

@@ -0,0 +1,38 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+    paths-ignore:
+      - 'CHANGELOG.md'
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+          fetch-depth: 0
+      - name: Generate a token
+        id: generate-token
+        uses: tibdex/github-app-token@v2
+        with:
+          app_id: ${{ secrets.SEMANTIC_RELEASE_APP_ID }}
+          private_key: ${{ secrets.SEMANTIC_RELEASE_KEY_PEM }}
+      - name: Release
+        uses: cycjimmy/semantic-release-action@v4
+        id: semantic-release
+        with:
+          semantic_version: 22.0.5
+          extra_plugins: |
+            @semantic-release/changelog@6.0.3
+            @semantic-release/git@10.0.1
+            conventional-changelog-conventionalcommits@7.0.2
+        env:
+          GITHUB_TOKEN: ${{ steps.generate-token.outputs.token }}

.gitignore

@@ -0,0 +1,2 @@
+node_modules
+vendor

.nvmrc

@@ -0,0 +1 @@
+v20.9.0

.releaserc.json

@@ -0,0 +1,43 @@
+{
+    "branches": [
+        "main"
+    ],
+    "plugins": [
+        [
+            "@semantic-release/commit-analyzer",
+            {
+                "preset": "conventionalcommits"
+            }
+        ],
+        [
+            "@semantic-release/release-notes-generator",
+            {
+                "preset": "conventionalcommits"
+            }
+        ],
+        [
+          "@semantic-release/github",
+          {
+            "successComment": "This ${issue.pull_request ? 'PR is included' : 'issue has been resolved'} in version ${nextRelease.version} :tada:",
+            "labels": false,
+            "releasedLabels": false
+          }
+        ],
+        [
+          "@semantic-release/changelog",
+          {
+            "changelogFile": "CHANGELOG.md",
+            "changelogTitle": "# Changelog\n\nAll notable changes to this project will be documented in this file."
+          }
+        ],
+        [
+          "@semantic-release/git",
+          {
+            "assets": [
+              "CHANGELOG.md"
+            ],
+            "message": "chore(release): version ${nextRelease.version}\n\n${nextRelease.notes}"
+          }
+        ]
+    ]
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,3 @@
+# Code of Conduct
+
+OBMS follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).

CONTRIBUTING.md

@@ -0,0 +1,71 @@
+# Contributing
+
+Thank you for your interest in contributing to our project! This guide will help you get started with contributing effectively.
+
+## Code of Conduct
+
+We expect all contributors to follow our Code of Conduct. Please be respectful and constructive in all interactions.
+
+## Getting Started
+
+1. Fork the repository
+2. Clone your fork locally
+3. Create a new branch for your changes
+4. Make your changes
+5. Push to your fork
+6. Submit a pull request
+
+## Development Process
+
+1. Check existing issues or create a new one to discuss proposed changes
+2. Fork the repository and create your branch from `main`
+3. Make your changes following our coding standards
+4. Add or update tests as needed
+5. Update documentation if required
+6. Ensure all tests pass locally
+7. Submit a pull request
+
+## Commit Guidelines
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/) specification for commit messages. This leads to more readable messages that are easy to follow when looking through the project history.
+
+## Pull Request Process
+
+- Ensure your pull request (PR) is focused on a single topic or issue.
+- Reference any relevant issues in your PR description (e.g., "Closes #123").
+- Provide a clear summary of your changes and the motivation behind them.
+- Ensure your code passes all tests and adheres to our coding standards.
+- Be responsive to feedback and make requested changes promptly.
+- PRs will be reviewed by maintainers and may require approval from multiple reviewers before merging.
+
+## Issue Reporting
+
+- Search existing issues before opening a new one to avoid duplicates.
+- Provide a clear and descriptive title.
+- Include steps to reproduce, expected behavior, and actual behavior.
+- Attach logs, screenshots, or code snippets if helpful.
+- Be respectful and constructive in your communication.
+
+## Coding Standards
+
+- Follow the language-specific style guides (e.g., PEP8 for Python, ESLint for JavaScript).
+- Write clear, maintainable, and well-documented code.
+- Include type annotations and docstrings/comments where appropriate.
+- Avoid introducing breaking changes unless discussed and approved.
+
+## Documentation
+
+- Update documentation for any user-facing changes.
+- Ensure code examples are up-to-date and accurate.
+- Use clear and concise language.
+- Follow the existing documentation structure and style.
+
+## Community Support
+
+- Join discussions in our community channels ([GitHub](https://github.com/forepath/obms-module-sdk/discussions) and [Discord](https://discord.gg/5wFMuVvQZM)).
+- Help others by answering questions and reviewing PRs.
+- Respect differing viewpoints and foster a welcoming environment.
+
+---
+
+Thank you for helping us improve this project! Your contributions make a difference.