Build docs and website on pull requests without publishing

Add a pull_request trigger to both the documentation and website
workflows, scoped to the paths that affect each build plus the workflow
file itself, so changes to these builds can be validated in CI before
they are merged.

The steps that check out the site repo, copy the built output, and open
a pull request against it are skipped for pull_request events, so a PR
build never publishes anywhere.

The website job's upstream-only guard is relaxed for pull requests;
without this, PR builds from forks would be skipped entirely. Push and
workflow_dispatch on a fork remain blocked as before.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: paulirwin

.github/workflows/Lucene-Net-Documentation.yml

@@ -32,6 +32,14 @@ name: 'Lucene.Net.Documentation'
 
 on:
   workflow_dispatch:
+  # 2026-08-09 - build (but do not publish) the API docs for any pull request that touches the docs sources, the docs
+  # plugins, or this workflow file. This lets changes to the docs build be validated in CI before they are merged.
+  # The steps that push to the site repo are skipped for pull requests - see the `if:` conditions below.
+  pull_request:
+    paths:
+    - 'websites/apidocs/**/*'
+    - 'src/docs/LuceneDocsPlugins/**/*'
+    - '.github/workflows/Lucene-Net-Documentation.yml'
   push:
     # 2026-06-23 - when both tags and branches are used, they are ORed. However, note that when paths is used, it is ANDed to each of them.
     tags:
@@ -188,13 +196,15 @@ jobs:
           path: '${{github.workspace}}/main-repo/websites/apidocs/_site'
 
       - name: Checkout Lucene.Net website
+        if: ${{ github.event_name != 'pull_request' }}
         uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
         with:
           repository: ${{ env.SITE_REPO }}
           ref: asf-site
           path: website-repo
 
       - name: Copy documentation site files
+        if: ${{ github.event_name != 'pull_request' }}
         run: |
           $source = "$Env:GITHUB_WORKSPACE\main-repo\websites\apidocs\_site"
           $dest = "$Env:GITHUB_WORKSPACE\website-repo\docs\$Env:RELEASE_VERSION"
@@ -212,6 +222,7 @@ jobs:
       # Because we are always building the docs against a consistent version
       - name: Create Pull Request
         id: cpr
+        if: ${{ github.event_name != 'pull_request' }}
         uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           token: ${{ secrets.LUCENE_NET_WEBSITE_BUILD }}
@@ -227,6 +238,7 @@ jobs:
             - For version ${{ env.RELEASE_VERSION }}
 
       - name: Check outputs
+        if: ${{ github.event_name != 'pull_request' }}
         run: |
           echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}"
           echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}"

.github/workflows/Lucene-Net-Website.yml

@@ -28,6 +28,13 @@ name: 'Lucene.Net.Website'
 
 on:
   workflow_dispatch:
+  # 2026-08-09 - build (but do not publish) the website for any pull request that touches the website sources or this
+  # workflow file. This lets changes to the website build be validated in CI before they are merged. The steps that push
+  # to the site repo are skipped for pull requests - see the `if:` conditions below.
+  pull_request:
+    paths:
+    - 'websites/site/**/*'
+    - '.github/workflows/Lucene-Net-Website.yml'
   push:
     # 2026-06-23 - when only tags and paths are used, they are ANDed together, not ORed, so the presence of a Website_* tag blocked the automation from triggering.
     # Howevever, if both tags and branches are present then we have 1) tags AND paths OR 2) branches AND paths. So, we need to specify them all if we want either or.
@@ -49,8 +56,10 @@ env:
 
 jobs:
   build:
-    # CRITICAL FIX: Only run this job if it is executing on the main upstream repository
-    if: github.repository == 'apache/lucenenet'
+    # CRITICAL FIX: Only run this job if it is executing on the main upstream repository, so that forks do not attempt
+    # to build and publish the website. Pull requests are exempt because they only build - the steps that publish to the
+    # site repo are skipped for pull requests (see the `if:` conditions below).
+    if: ${{ github.repository == 'apache/lucenenet' || github.event_name == 'pull_request' }}
     runs-on: windows-latest
     steps:
 
@@ -119,6 +128,7 @@ jobs:
           path: '${{github.workspace}}/main-repo/websites/site/_site'
 
       - name: Checkout Lucene.Net website
+        if: ${{ github.event_name != 'pull_request' }}
         uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
         with:
           repository: ${{ env.SITE_REPO }}
@@ -127,11 +137,13 @@ jobs:
           persist-credentials: false
 
       - name: Copy website files
+        if: ${{ github.event_name != 'pull_request' }}
         run: Get-ChildItem -Path "$Env:GITHUB_WORKSPACE\main-repo\websites\site\_site" | Copy-Item -Destination "$Env:GITHUB_WORKSPACE\website-repo" -Recurse -Force
         shell: powershell
 
       - name: Create Pull Request
         id: cpr
+        if: ${{ github.event_name != 'pull_request' }}
         uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # v7.0.8
         with:
           token: ${{ secrets.LUCENE_NET_WEBSITE_BUILD }}
@@ -147,6 +159,7 @@ jobs:
             For release version ${{ env.RELEASE_VERSION }}
 
       - name: Check outputs
+        if: ${{ github.event_name != 'pull_request' }}
         run: |
           echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}"
           echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}"