fix: ensure .nojekyll file is properly deployed to gh-pages branch

- Replace mkdocs gh-deploy with manual git deployment
- Ensures .nojekyll file is committed to gh-pages branch
- This will prevent Jekyll from processing the MkDocs output

Author: dataGriff

.github/workflows/deploy-docs.yml

@@ -25,13 +25,26 @@ jobs:
         run:  |     
           pip install mkdocs-material mkdocs-git-revision-date-localized-plugin pymdown-extensions mkdocs-mermaid2-plugin
 
-      # - name: Generate changelog
-      #   run: git-cliff -c cliff.toml
+      - name: Configure git
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "github-actions[bot]@users.noreply.github.com"
 
       - name: Build and Deploy
         run: |
+          # Build the site
           mkdocs build
+          
+          # Add .nojekyll to disable Jekyll processing
           touch site/.nojekyll
-          mkdocs gh-deploy --force
+          
+          # Deploy to gh-pages branch manually to ensure .nojekyll is included
+          cd site
+          git init
+          git add -A
+          git commit -m "Deploy MkDocs site"
+          git branch -M gh-pages
+          git remote add origin https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git
+          git push -f origin gh-pages
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}