ottu 0.0.0__tar.gz

ottu-0.0.0/.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# These owners will be the default owners for everything in the repo
+# and will automatically be requested for review on every pull request.
+*       @Infineon/epe-devops

ottu-0.0.0/.github/workflows/codespell.yml

@@ -0,0 +1,26 @@
+name: Codespell
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  codespell:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - uses: actions/checkout@v4
+    
+    - name: Install uv
+      uses: astral-sh/setup-uv@v2
+      with:
+        enable-cache: true
+    
+    - name: Set up Python
+      run: uv python install 3.11
+    
+    - name: Install dependencies
+      run: uv sync --all-extras
+    
+    - name: Check spelling with codespell
+      run: uv run codespell

ottu-0.0.0/.github/workflows/commit-check.yml

@@ -0,0 +1,57 @@
+name: Commit check
+
+on:
+  pull_request:
+  push:
+
+jobs:
+  commitlint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 100
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v7
+
+      - name: Install commitlint
+        run: |
+          npm install --save-dev @commitlint/cli @commitlint/config-conventional
+
+      - name: Compute commit range
+        id: range
+        shell: bash
+        run: |
+          if [ "${{ github.event_name }}" = "pull_request" ]; then
+            # For pull requests, GitHub checks out a synthetic merge commit whose
+            # parents are the base branch and the PR branch. We use their merge-base
+            # as the start of the valid range, so only commits introduced by the PR
+            # are checked.
+            git merge-base HEAD^1 HEAD^2 || git fetch --unshallow origin
+            FROM=$(git merge-base HEAD^1 HEAD^2)
+            TO=$(git rev-parse HEAD^2)
+          else
+            # For direct pushes, prefer the previous SHA when it is still in the
+            # current ancestry. After a rebase or force-push, the old SHA can be
+            # stale, so fall back to the merge-base with the parent branch and then
+            # to HEAD~1 as a last resort.
+            FROM="${{ github.event.before }}"
+            if ! git rev-parse --verify "$FROM" >/dev/null 2>&1 || ! git merge-base --is-ancestor "$FROM" HEAD >/dev/null 2>&1; then
+              FROM=$(git merge-base HEAD origin/main 2>/dev/null || git rev-parse HEAD~1)
+            fi
+            TO="${{ github.sha }}"
+          fi
+
+          echo "from=${FROM}" >> "$GITHUB_OUTPUT"
+          echo "to=${TO}" >> "$GITHUB_OUTPUT"
+
+      - name: Validate commit messages
+        shell: bash
+        run: |
+          echo "Checking commits between ${{ steps.range.outputs.from }} and ${{ steps.range.outputs.to }}..."
+          npx commitlint \
+            --from="${{ steps.range.outputs.from }}" \
+            --to="${{ steps.range.outputs.to }}" \
+            --config commitlint.config.js

ottu-0.0.0/.github/workflows/docs.yml

@@ -0,0 +1,32 @@
+name: Build docs
+
+on:
+  push:
+  pull_request:
+    paths:
+      - docs/**
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v7
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      with:
+        enable-cache: true
+
+    - name: Set up Python
+      run: uv python install 3.13
+
+    - name: Install docs dependencies with uv
+      run: uv sync --only-group docs --no-install-project
+
+    - name: Build docs
+      run: uv run -- make -C docs html

ottu-0.0.0/.github/workflows/format-check.yml

@@ -0,0 +1,32 @@
+name: Format check
+
+on:
+  push: &paths
+    paths:
+      - '.github/workflows/**'
+      - 'ottu/**/*.py'
+      - 'tests/**/*.py'
+      - '*.toml'
+  pull_request: *paths
+
+
+jobs:
+  format:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v7
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      with:
+        enable-cache: true
+
+    - name: Set up Python
+      run: uv python install 3.11
+
+    - name: Install dependencies
+      run: uv sync --all-extras
+
+    - name: Format check with Ruff
+      run: uv run ruff format --check --diff

ottu-0.0.0/.github/workflows/links-check.yml

@@ -0,0 +1,15 @@
+name: Links check
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+    tags:
+      - '*'
+  schedule:
+    - cron: '30 3 * * 4' # Run every Thursday at 3:30 AM UTC
+
+jobs:
+  linkChecker:
+    uses: Infineon/makers-devops/.github/workflows/check_links.yml@main

ottu-0.0.0/.github/workflows/lint.yml

@@ -0,0 +1,34 @@
+name: Lint
+
+on:
+  push: &paths
+    paths:
+      - '.github/workflows/**' 
+      - 'ottu/**/*.py'
+      - 'tests/**/*.py'
+      - '*.toml'
+  pull_request: *paths
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v7
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      with:
+        enable-cache: true
+
+    - name: Set up Python
+      run: uv python install 3.11
+
+    - name: Install dependencies
+      run: uv sync --all-extras
+
+    - name: Lint with Ruff
+      run: uv run ruff check --output-format=github
+
+    - name: Type check with mypy
+      run: uv run mypy --show-error-codes --pretty

ottu-0.0.0/.github/workflows/publish.yml

@@ -0,0 +1,47 @@
+name: Publish
+
+on:
+  push:
+    tags:
+      - "[0-9]+.[0-9]+.[0-9]*"
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/ottu/
+
+    steps:
+    - uses: actions/checkout@v7
+ 
+    - name: Install uv
+      uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+
+    - name: Set up Python
+      run: uv python install 3.11
+
+    - name: Install dependencies
+      run: uv sync --all-extras
+
+    - name: Format check
+      run: uv run ruff format --check
+
+    - name: Lint
+      run: uv run ruff check
+
+    - name: Type check
+      run: uv run mypy
+
+    - name: Run tests
+      run: uv run pytest
+
+    - name: Build distribution
+      run: uv build
+
+    - name: Publish to PyPI
+      run: uv publish

ottu-0.0.0/.github/workflows/tests.yml

@@ -0,0 +1,58 @@
+name: Tests
+
+on:
+  push: &paths
+    paths:
+      - '.github/workflows/**' 
+      - 'ottu/**/*.py'
+      - 'tests/**/*.py'
+      - '*.toml'
+  pull_request: *paths
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+
+    steps:
+    - uses: actions/checkout@v7
+    
+    - name: Install uv
+      uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      with:
+        enable-cache: true
+    
+    - name: Set up Python ${{ matrix.python-version }}
+      run: uv python install ${{ matrix.python-version }}
+    
+    - name: Install dependencies
+      run: uv sync --all-extras --python ${{ matrix.python-version }}
+    
+    - name: Run tests with pytest
+      run: uv run --python ${{ matrix.python-version }} pytest
+
+    - name: Upload coverage
+      if: matrix.python-version == '3.12'
+      uses: coverallsapp/github-action@v2
+      with:
+        file: ./coverage.xml
+        format: cobertura
+        github-token: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: Coverage Summary Report
+      if: matrix.python-version == '3.12'
+      run: |
+        echo "📊 [🔗 Coveralls Report](https://coveralls.io/builds/${{ github.sha }})" >> $GITHUB_STEP_SUMMARY
+
+    - name: Coverage Comment on PR
+      uses: orgoro/coverage@v3.2
+      if: matrix.python-version == '3.12' && github.event_name == 'pull_request'
+      with:
+        coverageFile: ./coverage.xml
+        token: ${{ secrets.GITHUB_TOKEN }}

ottu-0.0.0/.gitignore

@@ -0,0 +1,25 @@
+*.pyc
+__pycache__/
+*.egg-info/
+dist/
+build/
+.eggs/
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+ottu/_version.py
+*.bak
+.ruff_cache/
+.venv/
+venv/
+env/
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+.DS_Store
+.env
+.env.local
+*.log

ottu-0.0.0/.lycheeignore

@@ -0,0 +1,5 @@
+# Ignore local development and loopback URLs used in docs examples.
+^https?://(localhost|127\.0\.0\.1|0\.0\.0\.0|\[::1\]|10\.\d{1,3}\.\d{1,3}\.\d{1,3}|172\.(1[6-9]|2\d|3[01])\.\d{1,3}\.\d{1,3}|192\.168\.\d{1,3}\.\d{1,3})(:\d+)?/?$
+
+# npmjs.com is treated as a known 403 by the upstream service; ignore it in docs checks.
+^https://www\.npmjs\.com/?$

ottu-0.0.0/.pre-commit-config.yaml

@@ -0,0 +1,21 @@
+repos:
+  - repo: local
+    hooks:
+      - id: commitlint
+        name: commitlint
+        entry: npx --yes @commitlint/cli --config commitlint.config.js --edit
+        language: system
+        stages: [commit-msg]
+        pass_filenames: true
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.3
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+  - repo: https://github.com/codespell-project/codespell
+    rev: v2.4.3
+    hooks:
+      - id: codespell
+        name: codespell
+        args: ["--toml=pyproject.toml"]

ottu-0.0.0/.readthedocs.yaml

@@ -0,0 +1,22 @@
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the OS, Python version, and other tools you might need
+build:
+  os: ubuntu-24.04
+  tools:
+    python: "3.13"
+
+python:
+  install:
+    - method: uv
+      command: sync
+      groups:
+        - docs
+
+# Build documentation in the "docs/" directory with Sphinx
+sphinx:
+   configuration: docs/conf.py

ottu-0.0.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,89 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, contact the project team at maker@infineon.com.
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

ottu-0.0.0/CONTRIBUTING.md

@@ -0,0 +1,8 @@
+# Contributing
+
+The contribution guide for this project is maintained in the documentation on
+Read the Docs:
+
+- https://ottu.readthedocs.io/en/latest/contributing.html
+
+Please refer to that page for contribution steps, development setup, and followed conventions.

ottu-0.0.0/LICENSE

@@ -0,0 +1,23 @@
+# License
+
+MIT License
+
+Copyright (c) 2026 Infineon Technologies AG
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

ottu-0.0.0/PKG-INFO

@@ -0,0 +1,39 @@
+Metadata-Version: 2.5
+Name: ottu
+Version: 0.0.0
+Summary: CLI tool for embedded on-target testing
+Author-email: Infineon Technologies AG <maker@infineon.com>
+License: MIT
+License-File: LICENSE
+Keywords: cli,embedded,on-target,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Requires-Dist: click>=8.0.0
+Provides-Extra: dev
+Requires-Dist: codespell>=2.4.3; extra == 'dev'
+Requires-Dist: mypy>=2.3.1; extra == 'dev'
+Requires-Dist: pre-commit>=3.0.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.0.0; extra == 'dev'
+Requires-Dist: pytest>=7.0.0; extra == 'dev'
+Requires-Dist: ruff>=0.16.3; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: sphinx-rtd-theme>=3.0.2; extra == 'docs'
+Requires-Dist: sphinx<9.0,>=8.0; extra == 'docs'
+Description-Content-Type: text/markdown
+
+# ottu
+
+ottu (On-Target Testing Utility) is a CLI tool for on-target testing of embedded devices.
+
+> [!WARNING]
+> This repository is currently under development and is not yet ready for use.
+

ottu-0.0.0/README.md

@@ -0,0 +1,7 @@
+# ottu
+
+ottu (On-Target Testing Utility) is a CLI tool for on-target testing of embedded devices.
+
+> [!WARNING]
+> This repository is currently under development and is not yet ready for use.
+

ottu-0.0.0/SECURITY.md

@@ -0,0 +1,52 @@
+# Security Policy
+
+## Supported Versions
+
+The project maintainers will review security reports for the versions currently
+under active development. Please check the repository's release status and use
+current mainline code for reporting issues.
+
+| Version | Supported |
+| ------- | --------- |
+| main / latest | Yes |
+| older released versions | Not guaranteed |
+
+## Reporting a Vulnerability
+
+If you believe you have found a security vulnerability in this project, please
+report it privately and responsibly.
+
+Please email the maintainers at: maker@infineon.com
+
+When reporting, include:
+
+- a clear description of the vulnerability
+- affected version or branch
+- steps to reproduce the issue
+- the impact and risk assessment
+- any proposed fix or mitigation
+
+Please do not open a public GitHub issue for security problems until the issue has
+been triaged and a fix or mitigation is available.
+
+## Response Expectations
+
+We will make every effort to acknowledge your report promptly and to work with
+you to understand and remediate the issue. We ask for reasonable time to assess
+and address the report before public disclosure.
+
+## Disclosure Policy
+
+We follow a coordinated disclosure process. Once a fix is available, we may
+publish a security advisory or release notes describing the issue and the
+mitigation, while keeping sensitive details limited to the minimum necessary.
+
+## Security Best Practices
+
+When contributing to the project:
+
+- do not introduce unsafe patterns or insecure defaults
+- validate inputs and handle errors securely
+- avoid exposing secrets or credentials in code, logs, or documentation
+- report potential vulnerabilities privately as described above
+

ottu-0.0.0/commitlint.config.js

@@ -0,0 +1,40 @@
+module.exports = {
+  parserPreset: {
+    parserOpts: {
+      headerPattern: /^([a-zA-Z0-9_\-\/]+):\s(.*)$/,
+      headerCorrespondence: ['scope', 'subject'],
+    },
+  },
+
+  plugins: [
+    {
+      rules: {
+        'scope-subject-format': ({ header }) => {
+          const scopeSubjectRegex = /^[A-Za-z0-9_./\-]+:\s[A-Z].*\.$/;
+
+          return [
+            scopeSubjectRegex.test(header),
+            `Commit message must match style:\n` +
+              `  Expected: "path/to/file: Capitalized sentence description."\n` +
+              `  Received: "${header}"`,
+          ];
+        },
+
+        'signed-off-by': ({ raw }) => {
+          const signoffRegex = /(?:^|\n)Signed-off-by:\s.+<.+>\s*$/m;
+
+          return [
+            signoffRegex.test(raw),
+            'Commit message must include a Signed-off-by trailer.',
+          ];
+        },
+      },
+    },
+  ],
+
+  rules: {
+    'scope-subject-format': [2, 'always'],
+    'signed-off-by': [2, 'always'],
+    'header-max-length': [2, 'always', 78],
+  },
+};