From c525c3ae0d8b87354995d45879cb0c816014ff03 Mon Sep 17 00:00:00 2001 From: Danielle Adams Date: Wed, 11 Oct 2023 10:29:36 -0600 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4d0a21b..a8a388e 100644 --- a/README.md +++ b/README.md @@ -139,7 +139,7 @@ If changes are made to the action's [source code], the [usage examples] section ### Tests -The build and review PR workflow includes tests which are linked to a status check that needs to succeed before a PR is merged to the default branch. When a PR comes from a branch there should not be any issues running the tests. When a PR comes from a fork, tests may not have the required permissions or access to run since the `GITHUB_TOKEN` only has `read` access set for all scopes and fork's cannot access other secrets in the repository. In these scenarios, a fork may need to be merged into an intermediate branch by the repository owners to ensure the tests run successfully prior to a merge to the default branch. +The build and review PR workflow includes tests which are linked to a status check. That status check needs to succeed before a PR is merged to the default branch. When a PR comes from a branch, there should not be any issues running the tests. When a PR comes from a fork, tests may not have the required permissions or access to run since the `GITHUB_TOKEN` only has `read` access set for all scopes. Also, forks cannot access other secrets in the repository. In these scenarios, a fork may need to be merged into an intermediate branch by the repository owners to ensure the tests run successfully prior to merging to the default branch. ## Code of Conduct