Merge branch 'feature/composer-vendor-deploys' into staging

Author: ryanwelcher

.github/workflows/deploy-vendors.yml

@@ -28,6 +28,25 @@ jobs:
           php-version: '8.2'
           tools: composer
 
+      # ── Pre-create remote vendor directories ───────────────────────────────
+      # Runs once on first deploy when vendor/ doesn't exist yet on the server.
+      # lftp mkdir -fp is silent when the directory already exists.
+
+      - name: Ensure remote vendor directories exist
+        if: ${{ inputs.dry_run != true }}
+        env:
+          SFTP_USER: ${{ secrets.SFTP_USER }}
+          SFTP_PASSWORD: ${{ secrets.SFTP_PASSWORD }}
+        run: |
+          sudo apt-get install -y lftp
+          mkdir -p ~/.ssh
+          echo "${{ secrets.SFTP_KNOWN_HOSTS }}" >> ~/.ssh/known_hosts
+          lftp -e "
+            mkdir -fp htdocs/wp-content/plugins/bifrost-music/vendor;
+            mkdir -fp htdocs/wp-content/themes/bifrost-noise/vendor;
+            quit
+          " -u "$SFTP_USER,$SFTP_PASSWORD" sftp://sftp.wp.com
+
       # ── Plugin ─────────────────────────────────────────────────────────────
 
       - name: Install plugin dependencies (bifrost-music)

readme.md

@@ -79,7 +79,13 @@ The destination server and paths are hardcoded in the workflow file itself (`sft
 
 To include a new plugin or theme in the automated vendor deployment:
 
-**1. Edit [`.github/workflows/deploy-vendors.yml`](.github/workflows/deploy-vendors.yml)** and add two steps following the same pattern as the existing ones.
+**1. Edit [`.github/workflows/deploy-vendors.yml`](.github/workflows/deploy-vendors.yml)** and make two changes.
+
+Add a line to the **"Ensure remote vendor directories exist"** step:
+
+```bash
+mkdir -fp htdocs/wp-content/plugins/your-package-name/vendor;
+```
 
 Add a `composer install` step: