Remove Coverity Scan integration as not working

Author: NikolajSchlej

.github/workflows/main.yml

@@ -367,31 +367,32 @@ jobs:
           path: ${{runner.workspace}}/dist/*.zip
 
 # Static Analysis
-  build_analyze_linux_coverity:
-    env:
-      PROJECT_TYPE: TOOL
-      JOB_TYPE: COVERITY
-    if: github.repository_owner == 'LongSoft' && github.event_name != 'pull_request'
-    name: Coverity Static Analysis (shared Qt 6.5.0)
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-      - name: Install Qt
-        uses: jurplel/install-qt-action@v3
-        with:
-          version: '6.5.0'
-          host: 'linux'
-          target: 'desktop'
-      - name: Create build directory
-        run: cmake -E make_directory ${{runner.workspace}}/build
-      - name: Configure everything
-        working-directory: ${{runner.workspace}}/build
-        run: cmake ../UEFITool
-      - name: Run Coverity
-        working-directory: ${{runner.workspace}}/build
-        run: |
-          src=$(/usr/bin/curl -Lfs https://raw.githubusercontent.com/acidanthera/ocbuild/master/coverity/covstrap-linux.sh) && eval "$src" || exit 1
-        env:
-          COVERITY_SCAN_TOKEN: ${{ secrets.COVERITY_SCAN_TOKEN }}
-          COVERITY_SCAN_EMAIL: ${{ secrets.COVERITY_SCAN_EMAIL }}
-          COVERITY_BUILD_COMMAND: cmake --build .
+# Coverity is currently broken, stub it out for now
+#  build_analyze_linux_coverity:
+#    env:
+#      PROJECT_TYPE: TOOL
+#      JOB_TYPE: COVERITY
+#    if: github.repository_owner == 'LongSoft' && github.event_name != 'pull_request'
+#    name: Coverity Static Analysis (shared Qt 6.5.0)
+#    runs-on: ubuntu-latest
+#    steps:
+#      - uses: actions/checkout@v6
+#      - name: Install Qt
+#        uses: jurplel/install-qt-action@v3
+#        with:
+#          version: '6.5.0'
+#          host: 'linux'
+#          target: 'desktop'
+#      - name: Create build directory
+#        run: cmake -E make_directory ${{runner.workspace}}/build
+#      - name: Configure everything
+#        working-directory: ${{runner.workspace}}/build
+#        run: cmake ../UEFITool
+#      - name: Run Coverity
+#        working-directory: ${{runner.workspace}}/build
+#        run: |
+#          src=$(/usr/bin/curl -Lfs https://raw.githubusercontent.com/acidanthera/ocbuild/master/coverity/covstrap-linux.sh) && eval "$src" || exit 1
+#        env:
+#          COVERITY_SCAN_TOKEN: ${{ secrets.COVERITY_SCAN_TOKEN }}
+#          COVERITY_SCAN_EMAIL: ${{ secrets.COVERITY_SCAN_EMAIL }}
+#          COVERITY_BUILD_COMMAND: cmake --build .

README.md

@@ -54,10 +54,6 @@ You can either use [pre-built binaries](https://github.com/LongSoft/UEFITool/rel
 * Intel Firmware Interface Table (FIT) editing is not supported right now. FIT contains pointers to various image components that must be loaded before executing the first CPU instruction from the BIOS chip. Those components include CPU microcode updates, binaries and settings used by BIOS Guard and Boot Guard technologies and some other stuff. More information on FIT can be obtained [here](https://edc.intel.com/content/www/us/en/design/products-and-solutions/software-and-services/firmware-and-bios/firmware-interface-table/firmware-interface-table/).
 * Windows builds of `UEFIExtract` and `UEFIFind` might encouter an issue with folder paths being longer than 260 bytes (`MAX_PATH`) on some input files (see [issue #363](https://github.com/LongSoft/UEFITool/issues/363)). This is a [known Windows limitation](https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry), that can be fixed by enabling long paths support via Windows Registry and adding a manifest to the executable file that requires such support. `UEFIExtract` has the required manifest additions since version `A67`, and the required registry file is provided by Microsoft on the page linked above, but this workaround is only awailable starting with Windows 10 build 1067.   
 
-## Bug repellents
-
-* [Coverity Scan](https://scan.coverity.com/projects/17209) - static analyzer for C, C++, C#, JavaScript, Ruby, or Python code.
-
 ## GUID Database
 
 Every new release includes an update to the database of known UEFI-related GUIDs build with help of [Linux Vendor Firmware Service](https://fwupd.org).