Update ReadMe for Release Notes Generation Script (#14989)

Author: anupriya13

change/@rnw-scripts-generate-release-notes-d4a4f9cb-19ee-4dac-a467-95b8a8365643.json

@@ -0,0 +1,7 @@
+{
+  "type": "patch",
+  "comment": "Update ReadMe for Release Notes Generation Script",
+  "packageName": "@rnw-scripts/generate-release-notes",
+  "email": "[email protected]",
+  "dependentChangeType": "patch"
+}

packages/@rnw-scripts/generate-release-notes/ReadMe.md

@@ -29,15 +29,21 @@ or at least repo:status, repo_deployment, public_repo (for public repos)
 - Click that button to authorize the token with the organization.
 - Copy the generated token
 
-#### 2. Set env variables at root of the repo
+#### 2. Set variables as params and run "yarn release-notes"
 
 ```
-set GITHUB_TOKEN=<your-personal-access-token>
-set RELEASE_TAG=0.80.0
-set START_DATE=2025-06-01
-set END_DATE=2025-07-16
-
+Usage:
+  yarn release-notes --token <GITHUB_TOKEN> --start <START_DATE> --end <END_DATE> [--repo <OWNER/REPO>] [--tag <RELEASE_TAG>]
+
+Options:
+  --token       (required) GitHub personal access token.
+  --start       (required) Start date in YYYY-MM-DD.
+  --end         (required) End date in YYYY-MM-DD.
+  --repo        Repository in OWNER/REPO format. Default: microsoft/react-native-windows
+  --tag         Release tag label. Default: Unreleased. Expected: 0.80 or similar
+  --help        Show this help message.
 ```
-#### 3. Run "`yarn release-notes`" at the root of the repo
 
-#### 4. You will see a release-notes.md file generated at packages\@rnw-scripts\generate-release-notes\release_notes.md which will have all the data you need.
+#### 3. You will see a release-notes.md file generated at packages\@rnw-scripts\generate-release-notes\release_notes.md which will have all the data you need.
+
+#### 4. Verify the release notes generated from all commits section and delete the "All Commits" and "Excluded" sections after validation

packages/@rnw-scripts/generate-release-notes/generate-release-notes.js

@@ -189,8 +189,8 @@ function shouldIncludeInReleaseNotes(prDescription) {
   if (lines.length === 0) return false;
 
   // Check if the first non-empty line contains "no" or "_no_"
-  const firstLine = lines[0].toLowerCase();
-  return !(firstLine.includes('no') || firstLine.includes('_no_'));
+  const firstLine = lines[0].toLowerCase().trim();
+  return !(firstLine === 'no' || firstLine === '_no_');
 }
 
 function extractReleaseNotesSummary(prDescription) {
@@ -270,7 +270,8 @@ function extractTypeOfChange(prDescription) {
 
 async function categorizeCommits(commits) {
   const categories = {
-    'All Commits': [],
+    'All Commits [REVIEW ONLY]': [],
+    'Excluded [REVIEW ONLY]': [],
     'Breaking Changes': [],
     'New Features': [],
     'Reliability': [],
@@ -331,14 +332,16 @@ async function categorizeCommits(commits) {
           console.log(`PR #${prNumber}: Type of Change = "${typeOfChange}", Category = "${category}"`);
         } else {
           console.log(`Skipping PR #${prNumber} - not marked for inclusion in release notes`);
+          const excluded = `- ${commitTitle} [${commitTitle} · ${REPO}@${sha} (github.com)](${url})`;
+          categories['Excluded [REVIEW ONLY]'].push(excluded);
           continue; // Skip this commit
         }
       }
     }
 
     const entry = `- ${summary} [${commitTitle} · ${REPO}@${sha} (github.com)](${url})`;
 
-    categories['All Commits'].push(entry);
+    categories['All Commits [REVIEW ONLY]'].push(entry);
     categories[category].push(entry);
   }