Update .gitea/workflows/build.yaml

.gitea/workflows/build.yaml

@@ -7,19 +7,29 @@ jobs:
   build-macos:
     runs-on: macos-latest  # Runs on your Mac Mini
     steps:
-      - name: Checkout w/ Submodules
+      - name: Manual Checkout (Debug)
-        uses: actions/checkout@v3
+        env:
-        with:
+          # This token is automatically provided by Gitea to allow cloning
-          # 1. recursive: Grabs the main repo AND all nested layers of submodules
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          submodules: recursive
+        run: |
+          # 1. Clean the workspace to ensure a fresh start
+          echo "Cleaning workspace..."
+          rm -rf *
 
-          # 2. fetch-depth: 0 means "Download Everything" (Full History).
+          # 2. Force Git to use HTTPS (Fixes 'hangs' if submodules use git:// or git@)
-          #    Why? Shallow clones (depth: 1) often fail with submodules because
+          git config --global url."https://github.com/".insteadOf "git@github.com:"
-          #    the specific commit the submodule points to might be buried deep in history.
+          git config --global url."https://github.com/".insteadOf "git://github.com/"
-          fetch-depth: 0
+          git config --global url."https://codeberg.org/".insteadOf "git@codeberg.org:"
 
-          # 3. LFS: Just in case they store binary assets (images, test dbs) in Git LFS.
+          # 3. Clone the main repo from YOUR Gitea
-          lfs: true
+          # We use the token to authenticate seamlessly
+          echo "Cloning main repository..."
+          git clone https://user:$GITHUB_TOKEN@git.such.software/${{ github.repository }}.git .
+
+          # 4. Manually update submodules
+          # This will show us EXACTLY which submodule fails if one is broken
+          echo "Initializing submodules..."
+          git submodule update --init --recursive
 
       - name: Prepare Environment
         run: |