From 8348cd8bfdd37f05c09515eccb352e8fbc99f103 Mon Sep 17 00:00:00 2001
From: Benoit Donneaux <benoit@leastauthority.com>
Date: Tue, 19 Aug 2025 10:35:28 +0200
Subject: [PATCH] Support checks in forked repositories

Signed-off-by: Benoit Donneaux <benoit@leastauthority.com>
---
 .forgejo/workflows/jekyll.yaml        | 3 ++-
 .forgejo/workflows/jekyll_cleanup.yml | 1 +
 README.md                             | 1 +
 3 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/.forgejo/workflows/jekyll.yaml b/.forgejo/workflows/jekyll.yaml
index 9ec32f6..683012e 100644
--- a/.forgejo/workflows/jekyll.yaml
+++ b/.forgejo/workflows/jekyll.yaml
@@ -56,6 +56,7 @@ jobs:
           jekyll build --verbose
       - name: Deploy Jekyll site
         id: deploy_site
+        if: ${{ ! forge.event.pull_request.head.repo.fork }}
         run: |
           if [ "${{ forge.ref }}" = 'refs/heads/main' ]; then
             WEB_ROOT="${WEB_DIR}/live"
@@ -79,7 +80,7 @@ jobs:
             ./_site/ "${WEB_USER}@${WEB_HOST}:${WEB_ROOT}${WEB_CONTEXT}"
       - name: Comment pull request
         id: comment_pull_request
-        if: ${{ always() && forge.event_name == 'pull_request' }}
+        if: ${{ always() && forge.event_name == 'pull_request' && ! forge.event.pull_request.head.repo.fork }}
         uses: https://github.com/exercism/pr-commenter-action@v1.5.1
         with:
           template-variables: |
diff --git a/.forgejo/workflows/jekyll_cleanup.yml b/.forgejo/workflows/jekyll_cleanup.yml
index f3422e9..77a9b77 100644
--- a/.forgejo/workflows/jekyll_cleanup.yml
+++ b/.forgejo/workflows/jekyll_cleanup.yml
@@ -12,6 +12,7 @@ env:
   WEB_CONTEXT: "/${{ forge.event.pull_request.number }}/"
 jobs:
   jekyll_cleanup:
+    if: ${{ ! forge.event.pull_request.head.repo.fork }}
     runs-on: ubuntu-22.04
     permissions:
       pull-requests: read
diff --git a/README.md b/README.md
index 1e2f062..b16b693 100644
--- a/README.md
+++ b/README.md
@@ -21,3 +21,4 @@ docker-compose up
 
 We welcome contributions!  Easiest is to open tickets or pull requests directly.  If unsure, join the IRC or ask on the Tahoe-LAFS developer mailing list.
 
+**Caveat**: because they need access to the repository secrets (e.g. SSH private key), the deployment step will be skipped on forked repositories. Which means preview sites will only be published from local branches pushed by collaborators with permissions to write in this repository.