fix: explicitly configure git remote to use PAT_TOKEN for pushes (#235)

* fix: use PAT_TOKEN to bypass branch protection in release workflow

Allows the cargo-workspaces release workflow to push version bump commits
to the main branch by using a Personal Access Token with bypass permissions
when available, falling back to GITHUB_TOKEN otherwise.

* fix: explicitly configure git remote to use PAT_TOKEN for pushes

cargo-workspaces uses git internally for pushes and needs the remote URL
to be configured with the PAT token to bypass branch protection rules.
This ensures the PAT_TOKEN is used for git push operations, not just checkout.

Author: joshrotenberg

.github/workflows/cargo-workspaces-release.yml

@@ -57,6 +57,15 @@ jobs:
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
 
+          # Configure git remote to use PAT_TOKEN for pushes
+          if [ -n "${{ secrets.PAT_TOKEN }}" ]; then
+            echo "Configuring git to use PAT_TOKEN for pushes"
+            git remote set-url origin https://x-access-token:${{ secrets.PAT_TOKEN }}@github.com/${{ github.repository }}.git
+          else
+            echo "PAT_TOKEN not available, using GITHUB_TOKEN"
+            git remote set-url origin https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git
+          fi
+
       - name: Verify authentication (non-dry-run)
         if: ${{ !inputs.dry_run }}
         env: