Sync to the reference site's main branch; promote by workflow

The reference site now deploys from a single `main` branch, with the target
environment chosen by a marker in the commit message. Point the sync at that
branch and label its commits for staging.

Replace the production-branch copycat with a promote-only job. It copies no
files: content reaches the site solely through `main`, so the two branches can
no longer drift into different trees. Pushing this branch still publishes the
product live, exactly as it does today.

Also pin the copycat action to the commit that v3 resolves to, and drop the
pull_request trigger, which only produced redundant syncs.

Author: vladimir-litvinchik

.github/workflows/main.yml

@@ -1,35 +1,31 @@
-# This is a basic workflow to help you get started with Actions
+name: SyncToReferenceSite
 
-name: CopyChangesToMainRepo
-
-# Controls when the action will run. 
+# Copies this repo's tree into reference.groupdocs.com at
+# content/sites/groupdocs/conversion/ on `main` — the site's single deploy branch.
+#
+# The commit message carries [deploy-qa], so the site deploys it to STAGING only
+# (reference2.groupdocs.com). To publish it live, run the PromoteToProduction workflow.
 on:
-  # Triggers the workflow on push or pull request events but only for the main branch
   push:
     branches: [ main ]
-  pull_request:
-    branches: [ main ]
-
-  # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
 
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
-  # This workflow contains a single job called "build"
   build:
-    # The type of runner that the job will run on
     runs-on: ubuntu-latest
-
-    # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
     - name: Copycat
-      uses: andstor/copycat-action@v3
+      uses: andstor/copycat-action@c2b0316e9ab883478a4a7d40a4fcb03d17f281aa   # v3
       with:
         personal_token: ${{ secrets.REPO_TOKEN }}
         src_path: /.
+        # ⚠️ The trailing slash is load-bearing. copycat empties `${DST_PATH%/*}`, which is
+        # `.../conversion` only while the trailing slash is present — drop it and that becomes
+        # `.../groupdocs`, wiping EVERY product's content from the site repo.
         dst_path: /content/sites/groupdocs/conversion/
         dst_owner: groupdocs
         dst_repo_name: reference.groupdocs.com
         dst_branch: main
         src_branch: main
         clean: true
+        commit_message: 'Update file(s) from ${{ github.repository }} [deploy-qa]'

.github/workflows/production.yml

@@ -1,35 +1,24 @@
-# This is a basic workflow to help you get started with Actions
+name: PromoteToProduction
 
-name: CopyChangesToProductionRepo
-
-# Controls when the action will run. 
+# Publishes this product's API reference to the LIVE site (reference.groupdocs.com).
+#
+# Copies NO files. Content reaches the site only through `main` (see SyncToReferenceSite);
+# this just asks the site to deploy the conversion content currently on `main` to production.
+# That is what keeps the two branches from ever holding different trees.
 on:
-  # Triggers the workflow on push or pull request events but only for the main branch
   push:
     branches: [ production ]
-  pull_request:
-    branches: [ production ]
-
-  # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
 
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
-  # This workflow contains a single job called "build"
-  build:
-    # The type of runner that the job will run on
+  promote:
     runs-on: ubuntu-latest
-
-    # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
-    - name: Copycat
-      uses: andstor/copycat-action@v3
-      with:
-        personal_token: ${{ secrets.REPO_TOKEN }}
-        src_path: /.
-        dst_path: /content/sites/groupdocs/conversion/
-        dst_owner: groupdocs
-        dst_repo_name: reference.groupdocs.com
-        dst_branch: production
-        src_branch: production
-        clean: true
+    - name: Deploy the current site `main` content for conversion to production
+      env:
+        GH_TOKEN: ${{ secrets.REPO_TOKEN }}
+      run: |
+        gh workflow run deploy_conversion.yml \
+          --repo groupdocs/reference.groupdocs.com \
+          --ref main \
+          -f environment=production