Add manual workflow to comment on existing release notes PRs

Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>

Author: Copilot

.github/scripts/README.md

@@ -8,6 +8,18 @@ This PowerShell script adds a reminder comment to all open PRs that modify the `
 
 ### Usage
 
+**Option 1: Use the GitHub Workflow (Recommended)**
+
+The easiest way to add comments to existing PRs is to use the manual workflow:
+
+1. Go to the Actions tab in the repository
+2. Select "Comment on Existing Release Notes PRs" workflow
+3. Click "Run workflow"
+4. Choose whether to run in dry-run mode (to preview which PRs will be commented)
+5. Click "Run workflow"
+
+**Option 2: Run the PowerShell Script Locally**
+
 ```powershell
 # Set your GitHub token as an environment variable
 $env:GITHUB_TOKEN = "your-github-token-here"
@@ -37,4 +49,4 @@ pwsh .github/scripts/comment-on-existing-release-notes-prs.ps1
 
 ### Note
 
-For new PRs, the automated workflow `.github/workflows/check-release-notes-prs.yml` will automatically add the comment. This script is only needed to handle existing open PRs at the time of deployment.
+For new PRs, the automated workflow `.github/workflows/check-release-notes-prs.yml` will automatically add the comment. This script/workflow is only needed to handle existing open PRs at the time of deployment.

.github/workflows/comment-on-existing-release-notes-prs.yml

@@ -0,0 +1,95 @@
+name: Comment on Existing Release Notes PRs
+
+on:
+  workflow_dispatch:
+    inputs:
+      dryRun:
+        description: 'Dry run mode (only list PRs, do not add comments)'
+        required: false
+        default: 'false'
+        type: choice
+        options:
+          - 'true'
+          - 'false'
+
+permissions:
+  pull-requests: write
+  contents: read
+  issues: write
+
+jobs:
+  comment-on-prs:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add Comments to Existing PRs
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const dryRun = '${{ inputs.dryRun }}' === 'true';
+            
+            // PRs that modify RELEASENOTES.md
+            const prs = [2056, 2049, 2048, 2047, 2041, 2033, 2031, 2029, 2010, 1994, 1882, 1828, 1824, 1795];
+            
+            const comment = `### ⚠️ Release Notes Update Reminder
+
+Thank you for updating the release notes! 
+
+Please ensure that your changes are placed **above the new version section** (currently \`## v8.1\`) in the RELEASENOTES.md file.
+
+This helps maintain a clear changelog structure where new changes are grouped under the latest unreleased version.`;
+            
+            console.log(`Processing ${prs.length} PRs...`);
+            console.log(`Dry run mode: ${dryRun}`);
+            console.log('');
+            
+            let commented = 0;
+            let skipped = 0;
+            let failed = 0;
+            
+            for (const prNumber of prs) {
+              try {
+                console.log(`Checking PR #${prNumber}...`);
+                
+                // Check if comment already exists
+                const comments = await github.rest.issues.listComments({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: prNumber,
+                });
+                
+                const alreadyCommented = comments.data.some(c => 
+                  c.body && c.body.includes('Release Notes Update Reminder')
+                );
+                
+                if (alreadyCommented) {
+                  console.log(`  ℹ️ Comment already exists on PR #${prNumber}, skipping...`);
+                  skipped++;
+                  continue;
+                }
+                
+                if (dryRun) {
+                  console.log(`  [DRY RUN] Would add comment to PR #${prNumber}`);
+                  commented++;
+                } else {
+                  // Add comment
+                  await github.rest.issues.createComment({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: prNumber,
+                    body: comment
+                  });
+                  console.log(`  ✓ Comment added to PR #${prNumber}`);
+                  commented++;
+                }
+              } catch (error) {
+                console.log(`  ✗ Failed to process PR #${prNumber}: ${error.message}`);
+                failed++;
+              }
+            }
+            
+            console.log('');
+            console.log('Summary:');
+            console.log(`  Total PRs processed: ${prs.length}`);
+            console.log(`  Comments added: ${commented}`);
+            console.log(`  Skipped (already commented): ${skipped}`);
+            console.log(`  Failed: ${failed}`);

docs/release-notes-pr-automation.md

@@ -32,18 +32,27 @@ This workflow automatically triggers when a PR is opened, updated, or reopened i
 
 ### 2. One-Time Script for Existing PRs
 
-**File**: `.github/scripts/comment-on-existing-release-notes-prs.ps1`
+**Files**: 
+- `.github/scripts/comment-on-existing-release-notes-prs.ps1` (PowerShell script)
+- `.github/workflows/comment-on-existing-release-notes-prs.yml` (Manual workflow)
 
-This PowerShell script is designed to be run once to add comments to all currently open PRs that modify `RELEASENOTES.md`. After the initial run, the automated workflow handles new PRs.
+These are designed to be run once to add comments to all currently open PRs that modify `RELEASENOTES.md`. After the initial run, the automated workflow handles new PRs.
 
-**Usage:**
+**Usage (Recommended - Manual Workflow):**
+1. Go to the Actions tab in the repository
+2. Select "Comment on Existing Release Notes PRs" workflow
+3. Click "Run workflow"
+4. Choose whether to run in dry-run mode (preview only)
+5. Click "Run workflow" to execute
+
+**Usage (Alternative - PowerShell Script):**
 ```powershell
 $env:GITHUB_TOKEN = "your-token-here"
 pwsh .github/scripts/comment-on-existing-release-notes-prs.ps1
 ```
 
-The script:
-1. Fetches all open PRs
+What it does:
+1. Fetches all open PRs (or uses a predefined list)
 2. Checks which ones modify `RELEASENOTES.md`
 3. Adds the reminder comment (if not already present)