Synch changes with a neer repo.

.checkov.yml

@@ -0,0 +1,4 @@
+# You can see all available properties here: https://github.com/bridgecrewio/checkov#configuration-using-a-config-file
+quiet: true
+skip-check:
+  - CKV_DOCKER_2

.codespellrc

@@ -1,4 +1,4 @@
 [codespell]
-skip = build,*.yuv,components/fatfs/src/*,alice.txt,*.rgb,components/wpa_supplicant/*,components/esp_wifi/*
+skip = build,*.yuv,components/fatfs/src/*,alice.txt,*.rgb,components/wpa_supplicant/*,components/esp_wifi/*,.github/styles/vale/*
 ignore-words-list = ser,dout,rsource,fram,inout,shs,ans,aci,unstall,unstalling,hart,wheight,wel
 write-changes = false

.devskim.json

@@ -0,0 +1,3 @@
+{
+  "Globs": ["**/.git/**", "**/megalinter-reports/**"]
+}

.eslintignore

@@ -0,0 +1,5 @@
+node_modules
+docs/node_modules
+coverage
+app/templates
+**/templates

.eslintrc.json

@@ -0,0 +1,17 @@
+{
+  "root": true,
+  "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": {"project": ["./docs/tsconfig.json"]},
+  "plugins": ["@typescript-eslint"],
+  "rules": {
+    "@typescript-eslint/strict-boolean-expressions": [
+      2,
+      {
+        "allowString": false,
+        "allowNumber": false
+      }
+    ]
+  },
+  "ignorePatterns": ["src/**/*.test.ts", "docs/**/*.test.ts"]
+}

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -0,0 +1,38 @@
+labels: [idea]
+body:
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checked
+      description: Please confirm and check all the following options.
+      options:
+        - label: I searched existing ideas and did not find a similar one
+          required: true
+        - label: I added a very descriptive title
+          required: true
+        - label: I've clearly described the feature request and motivation for it
+          required: true
+  - type: textarea
+    id: feature-request
+    validations:
+      required: true
+    attributes:
+      label: Feature request
+      description: |
+        A clear and concise description of the feature proposal. Please provide links to any relevant GitHub repos, papers, or other resources if relevant.
+  - type: textarea
+    id: motivation
+    validations:
+      required: true
+    attributes:
+      label: Motivation
+      description: |
+        Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too.
+  - type: textarea
+    id: proposal
+    validations:
+      required: false
+    attributes:
+      label: Proposal (If applicable)
+      description: |
+        If you would like to propose a solution, please describe it here.

.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -0,0 +1,108 @@
+labels: [Question]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your interest in jmbde-QT 🦜️🔗!
+
+        Please follow these instructions, fill every question, and do every step. 🙏
+
+        We're asking for this because answering questions and solving problems in GitHub takes a lot of time --
+        this is time that we cannot spend on adding new features, fixing bugs, writing documentation or reviewing pull requests.
+
+        By asking questions in a structured way (following this) it will be much easier for us to help you.
+
+        There's a high chance that by following this process, you'll find the solution on your own, eliminating the need to submit a question and wait for an answer. 😎
+
+        As there are many questions submitted every day, we will **DISCARD** and close the incomplete ones.
+
+        That will allow us (and others) to focus on helping people like you that follow the whole process. 🤓
+
+        Relevant links to check before opening a question to see if your question has already been answered, fixed or
+        if there's another way to solve your problem:
+
+        [jmbde-QT documentation with the integrated search](https://jmuelbert.github.io/jmbde-QT/),
+        [API Reference](https://jmuelbert.github.io/jmbde-QT/developerapi/),
+        [GitHub search](https://github.com/jmuelbert/jmbde-QT],
+        [jmbde-java Github Discussions](https://github.com/jmuelbert/jmbde-QT/discussions),
+        [jmbde-java Github Issues](https://github.com/jmuelbert/jmbde-QT/issues?q=is%3Aissue),
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checked other resources
+      description: Please confirm and check all the following options.
+      options:
+        - label: I added a very descriptive title to this question.
+          required: true
+        - label: I searched the jmbde-QT documentation with the integrated search.
+          required: true
+        - label: I used the GitHub search to find a similar question and didn't find it.
+          required: true
+  - type: checkboxes
+    id: help
+    attributes:
+      label: Commit to Help
+      description: |
+        After submitting this, I commit to one of:
+
+          * Read open questions until I find 2 where I can help someone and add a comment to help there.
+          * I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
+          * Once my question is answered, I will mark the answer as "accepted".
+      options:
+        - label: I commit to help with one of those options 👆
+          required: true
+  - type: textarea
+    id: example
+    attributes:
+      label: Example Code
+      description: |
+        Please add a self-contained, [minimal, reproducible, example](https://stackoverflow.com/help/minimal-reproducible-example) with your use case.
+
+        If a maintainer can copy it, run it, and see it right away, there's a much higher chance that you'll be able to get help.
+
+        **Important!**
+
+        * Use code tags (e.g., ```python ... ```) to correctly [format your code](https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting).
+        * INCLUDE the language label (e.g. `python`) after the first three backticks to enable syntax highlighting. (e.g., ```python rather than ```).
+        * Reduce your code to the minimum required to reproduce the issue if possible. This makes it much easier for others to help you.
+        * Avoid screenshots when possible, as they are hard to read and (more importantly) don't allow others to copy-and-paste your code.
+
+      placeholder: |
+        **
+
+      render: c++
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: |
+        What is the problem, question, or error?
+
+        Write a short description explaining what you are doing, what you expect to happen, and what is currently happening.
+      placeholder: |
+        * I'm trying to use the `jmbde-java` library to do X.
+        * I expect to see Y.
+        * Instead, it does Z.
+    validations:
+      required: true
+  - type: textarea
+    id: system-info
+    attributes:
+      label: System Info
+      description: |
+        Please share your system info with us.
+
+        "mvn --version" - Get the Java Version, the maven version and the OS version
+        platform (windows / linux / mac)
+
+        OR if you're on a recent version of jmbde-QT you can paste the output of:
+
+      placeholder: |
+        "mvn -v"
+        platform
+        Qt version
+
+    validations:
+      required: true

.github/dependabot.yml

@@ -2,41 +2,62 @@
 # To get started with Dependabot version updates, you'll need to specify which
 # package ecosystems to update and where the package manifests are located.
 # Please see the documentation for all configuration options:
-# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
 
 version: 2
 updates:
-  - package-ecosystem: "github-actions"
-    directory: "/"
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: github-actions
+    directory: /
     schedule:
-      interval: "daily"
+      interval: monthly
+    groups:
+      github-actions:
+        patterns:
+          - '*'
+    open-pull-requests-limit: 10
     commit-message:
-      prefix: ":rocket: gha"
+      include: scope
+      prefix: fix(gha)
 
-  - package-ecosystem: "docker"
-    directory: "/"
+  # Enable version updates for Docker
+  - package-ecosystem: docker
+    # Look for a `Dockerfile` in the `root` directory
+    directory: /
+    # Check for updates once a week
     schedule:
-      interval: "daily"
+      interval: monthly
     commit-message:
-      prefix: ":rocket: docker"
+      prefix: fix(docker)
 
-  - package-ecosystem: "bundler"
-    directory: "/"
+  # Maintain dependencies for nuget
+  - package-ecosystem: nuget # See documentation for possible values
+    directory: / # Location of package manifests
     schedule:
-      interval: "daily"
+      interval: monthly
     commit-message:
-      prefix: ":rocket: bundler"
+      prefix: fix(nuget)
 
-  - package-ecosystem: "npm"
-    directory: "/"
+  # Maintain dependencies for pip
+  - package-ecosystem: pip # See documentation for possible values
+    directory: / # Location of package manifests
     schedule:
-      interval: "daily"
+      interval: monthly
     commit-message:
-      prefix: ":rocket: npm"
+      prefix: fix(pip)
 
-  - package-ecosystem: "pip"
-    directory: "/"
+  # Maintain dependencies for npm
+  - package-ecosystem: npm
+    directory: /
     schedule:
-      interval: "daily"
+      interval: monthly
     commit-message:
-      prefix: ":rocket: pip"
+      prefix: fix(npm)
+
+  # Maintain dependencies for npm
+  - package-ecosystem: npm
+    directory: /docs
+    schedule:
+      interval: monthly
+    commit-message:
+      prefix: fix(npm for astrodoc)

.github/labeler.yml

@@ -0,0 +1,26 @@
+# Add 'root' label to any root file changes
+# Quotation marks are required for the leading asterisk
+'project':
+  - changed-files:
+      - any-glob-to-any-file: '*'
+      - all-globs-to-all-files: '!*.md'
+# Add 'Documentation' label to any change to .md files within the entire repository
+documentation:
+  - changed-files:
+      - any-glob-to-any-file: docs/**
+# Add 'source' label to any change to src files within the source dir EXCEPT for the docs sub-folder
+'source':
+  - changed-files:
+      - any-glob-to-any-file: src/**/*
+      - all-globs-to-all-files: '!src/docs/**'
+'github_actions':
+  - changed-files:
+      - any-glob-to-any-file:
+          - .github/actions/**
+          - .github/workflows/**
+# Add 'feature' label to any PR where the head branch name starts with `feature` or has a `feature` section in the name
+'feature':
+  - head-branch: [^feature, feature]
+# Add 'release' label to any PR that is opened against the `main` branch
+release:
+  - base-branch: release