From bb4f5bdcb048d66e190465256901c131d850fa9c Mon Sep 17 00:00:00 2001 From: Volodymyr Zotov Date: Wed, 22 Oct 2025 10:54:33 -0500 Subject: [PATCH] Update docs --- docs/fork-pr-testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/fork-pr-testing.md b/docs/fork-pr-testing.md index 303ac73..560133e 100644 --- a/docs/fork-pr-testing.md +++ b/docs/fork-pr-testing.md @@ -24,7 +24,7 @@ When a PR is created or updated: **Steps for maintainers:** 1. Go to the PR page -2. Click **"Approve workflow to run"** button +2. Click **"Approve workflow to run"** button. For contributors who have made more than one contribution, workflows will start automatically after approval. 3. The workflow will then execute **Note**: The `test-e2e.yml` workflow will still fail for external PRs even after approval, as it's designed to prevent automatic execution. Need to use the slash command instead. @@ -41,7 +41,7 @@ Once the initial checks have run (and failed), maintainers can test the PR using ``` /ok-to-test sha= ``` - Replace `` with the actual commit SHA from the PR. + Replace `` with the latest commit SHA from the PR. **Note**: Use the short SHA.