From 47a0e6b29838e17e42142ddd2053cf9cf89d1651 Mon Sep 17 00:00:00 2001 From: Peter Evans Date: Tue, 4 Aug 2020 14:27:36 +0900 Subject: [PATCH] Update documentation --- docs/examples.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/examples.md b/docs/examples.md index 277aa10..ca4be28 100644 --- a/docs/examples.md +++ b/docs/examples.md @@ -326,7 +326,8 @@ An `on: repository_dispatch` workflow can be triggered from another workflow wit This is a pattern that lends itself to automated code linting and fixing. A pull request can be created to fix or modify something during an `on: pull_request` workflow. The pull request containing the fix will be raised with the original pull request as the base. This can be then be merged to update the original pull request and pass any required tests. -Note that due to [limitations on forked repositories](https://docs.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token) workflows for this use case do not work for pull requests raised from forks. +Note that due to [token restrictions on public repository forks](https://docs.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token), workflows for this use case do not work for pull requests raised from forks. +Private repository forks can be configured to [enable workflows](https://docs.github.com/en/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks) to run without restriction. ### autopep8