ci: git: fix "Error in the HTTP2 framing layer"

For unknown reasons, the local development host and CI is
running in temporary "Error in the HTTP2 framing layer".
Forcing the historical but still supported HTTP/1.1 layer
seems to be a stable workaround - happened in Oct. 2023.

Signed-off-by: Stephan Linz <[email protected]>

.github/workflows/doc-build.yml

@@ -48,6 +48,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
+      - name: Apply container HTTP/2 framing layer workaround
+        run: |
+          # FIXME: For unknown reasons, the local development host and CI is
+          #        running in temporary "Error in the HTTP2 framing layer".
+          #        Forcing the historical but still supported HTTP/1.1 layer
+          #        seems to be a stable workaround - happened in Oct. 2023.
+          git config --global --add http.version HTTP/1.1
+
       - name: Update GitHub PATH for west
         run: |
           echo "$HOME/.local/bin" >> $GITHUB_PATH

.github/workflows/qa-compliance.yml

@@ -14,6 +14,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
+      - name: Apply container HTTP/2 framing layer workaround
+        run: |
+          # FIXME: For unknown reasons, the local development host and CI is
+          #        running in temporary "Error in the HTTP2 framing layer".
+          #        Forcing the historical but still supported HTTP/1.1 layer
+          #        seems to be a stable workaround - happened in Oct. 2023.
+          git config --global --add http.version HTTP/1.1
+
       - name: Update GitHub PATH for west
         run: |
           echo "$HOME/.local/bin" >> $GITHUB_PATH

.github/workflows/qa-integration.yml

@@ -55,6 +55,14 @@ jobs:
           #        GitHub comes up with a fundamental fix for this problem.
           git config --global --add safe.directory ${GITHUB_WORKSPACE}
 
+      - name: Apply container HTTP/2 framing layer workaround
+        run: |
+          # FIXME: For unknown reasons, the local development host and CI is
+          #        running in temporary "Error in the HTTP2 framing layer".
+          #        Forcing the historical but still supported HTTP/1.1 layer
+          #        seems to be a stable workaround - happened in Oct. 2023.
+          git config --global --add http.version HTTP/1.1
+
       - name: Update GitHub PATH for west
         run: |
           echo "$HOME/.local/bin" >> $GITHUB_PATH
@@ -156,6 +164,14 @@ jobs:
           #        GitHub comes up with a fundamental fix for this problem.
           git config --global --add safe.directory ${GITHUB_WORKSPACE}
 
+      - name: Apply container HTTP/2 framing layer workaround
+        run: |
+          # FIXME: For unknown reasons, the local development host and CI is
+          #        running in temporary "Error in the HTTP2 framing layer".
+          #        Forcing the historical but still supported HTTP/1.1 layer
+          #        seems to be a stable workaround - happened in Oct. 2023.
+          git config --global --add http.version HTTP/1.1
+
       - name: Update GitHub PATH for west
         run: |
           echo "$HOME/.local/bin" >> $GITHUB_PATH
@@ -269,6 +285,14 @@ jobs:
         board: [tiac_magpie]
 
     steps:
+      - name: Apply container HTTP/2 framing layer workaround
+        run: |
+          # FIXME: For unknown reasons, the local development host and CI is
+          #        running in temporary "Error in the HTTP2 framing layer".
+          #        Forcing the historical but still supported HTTP/1.1 layer
+          #        seems to be a stable workaround - happened in Oct. 2023.
+          git config --global --add http.version HTTP/1.1
+
       - name: Update GitHub PATH for west
         run: |
           echo "$HOME/.local/bin" >> $GITHUB_PATH