From 1af89831b53a239c68752225c05ad06fe5ae2370 Mon Sep 17 00:00:00 2001 From: osa22 Date: Wed, 22 May 2024 15:45:41 -0400 Subject: [PATCH 1/7] Update reusing-workflows.md Making access to reusable workflows clearer as evident in customer's confusion in the following tickets: [ZD_2783484](https://github.zendesk.com/agent/tickets/2783484) [ZD_2755805](https://github.zendesk.com/agent/tickets/2755805) --- content/actions/using-workflows/reusing-workflows.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 689771a0a275..4647b9726d63 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -59,6 +59,16 @@ A reusable workflow can be used by another workflow if any of the following is t - The called workflow is stored in a private repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion ghes or ghec %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-organization)" and "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository)."{% endif %} {% endif %} +In summary, the ability to access reusable workflow by the caller workflow is determined by the repository's visibility as shown in the table below. + +| Caller workflow's Repository | Accessible reusable workflow's Repositories | +|----|----| +| `private` | `private`, `internal`, and `public` | +| `internal` | `internal`, and `public` | +| `public` | `public` | + +In addition, please note that the **Actions permissions** on the caller's repository Actions settings page must be set to allow the use of actions and reusable workflows; and with the exception of a public repository, the **Access** policy on the called workflow's repository Actions settings page must also be explicitly configured to allow access from repositories in the organization or repositories in the enterprise. + {% data reusables.actions.actions-redirects-workflows %} ## Using runners From b579d2cd3ee146fdde2a635ceb537e684842f5c7 Mon Sep 17 00:00:00 2001 From: osa22 Date: Wed, 22 May 2024 16:00:37 -0400 Subject: [PATCH 2/7] Update reusing-workflows.md Making the statements even clearer. --- content/actions/using-workflows/reusing-workflows.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 4647b9726d63..e22be9f94293 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -59,15 +59,17 @@ A reusable workflow can be used by another workflow if any of the following is t - The called workflow is stored in a private repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion ghes or ghec %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-organization)" and "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository)."{% endif %} {% endif %} -In summary, the ability to access reusable workflow by the caller workflow is determined by the repository's visibility as shown in the table below. +In summary, the ability to access called workflow by the caller workflow is determined by the repository's visibility access as shown in the table below. -| Caller workflow's Repository | Accessible reusable workflow's Repositories | +| Caller repository | Accessible called workflow repositories | |----|----| | `private` | `private`, `internal`, and `public` | | `internal` | `internal`, and `public` | | `public` | `public` | -In addition, please note that the **Actions permissions** on the caller's repository Actions settings page must be set to allow the use of actions and reusable workflows; and with the exception of a public repository, the **Access** policy on the called workflow's repository Actions settings page must also be explicitly configured to allow access from repositories in the organization or repositories in the enterprise. +In addition, please note that the **Actions permissions** on the caller's repository Actions settings page must be set to allow the use of actions and reusable workflows. + +With the exception of a public repository, also note that the **Access** policy on the called workflow's repository Actions settings page must be explicitly configured to allow access from repositories in the organization or repositories in the enterprise. {% data reusables.actions.actions-redirects-workflows %} From cad7941f4ad98e1d2c738d18f2f57ab32afb15c1 Mon Sep 17 00:00:00 2001 From: osa22 Date: Wed, 22 May 2024 16:05:26 -0400 Subject: [PATCH 3/7] Update reusing-workflows.md Even clearer per Copilot suggestions. --- content/actions/using-workflows/reusing-workflows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index e22be9f94293..79bf61fbfdca 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -61,7 +61,7 @@ A reusable workflow can be used by another workflow if any of the following is t In summary, the ability to access called workflow by the caller workflow is determined by the repository's visibility access as shown in the table below. -| Caller repository | Accessible called workflow repositories | +| Caller repository | Accessible workflows repositories | |----|----| | `private` | `private`, `internal`, and `public` | | `internal` | `internal`, and `public` | From 3021f982e583aa91b0e7d6dcd28cf7c164fb4af3 Mon Sep 17 00:00:00 2001 From: osa22 Date: Wed, 22 May 2024 16:18:37 -0400 Subject: [PATCH 4/7] Update reusing-workflows.md ... --- content/actions/using-workflows/reusing-workflows.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 79bf61fbfdca..7bf401a43484 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -59,7 +59,7 @@ A reusable workflow can be used by another workflow if any of the following is t - The called workflow is stored in a private repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion ghes or ghec %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-organization)" and "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository)."{% endif %} {% endif %} -In summary, the ability to access called workflow by the caller workflow is determined by the repository's visibility access as shown in the table below. +In summary, for the called workflow to be reachable by the caller workflow, the repository's visibility must be as shown in the table below. | Caller repository | Accessible workflows repositories | |----|----| @@ -67,9 +67,9 @@ In summary, the ability to access called workflow by the caller workflow is dete | `internal` | `internal`, and `public` | | `public` | `public` | -In addition, please note that the **Actions permissions** on the caller's repository Actions settings page must be set to allow the use of actions and reusable workflows. +Additionaly, please note that the **Actions permissions** on the caller's repository Actions settings page must be configured to allow the use of actions and reusable workflows. -With the exception of a public repository, also note that the **Access** policy on the called workflow's repository Actions settings page must be explicitly configured to allow access from repositories in the organization or repositories in the enterprise. +Furthermore, except for a public repository, also note that the **Access** policy on the called workflow's repository Actions settings page must be explicitly configured to allow access from repositories in the organization or repositories in the enterprise. {% data reusables.actions.actions-redirects-workflows %} From cc57e9d5bcd70b5f32c2916c750b9e48a900242c Mon Sep 17 00:00:00 2001 From: hubwriter Date: Fri, 24 May 2024 15:46:22 +0100 Subject: [PATCH 5/7] Changes for docs writing style --- content/actions/using-workflows/reusing-workflows.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 7bf401a43484..15c1ad53d288 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -59,7 +59,7 @@ A reusable workflow can be used by another workflow if any of the following is t - The called workflow is stored in a private repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion ghes or ghec %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}"[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-organization)" and "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository)."{% endif %} {% endif %} -In summary, for the called workflow to be reachable by the caller workflow, the repository's visibility must be as shown in the table below. +The following table shows the accessibility of reusable workflows to a caller workflow, depending on the visibility of the host repository. | Caller repository | Accessible workflows repositories | |----|----| @@ -67,9 +67,9 @@ In summary, for the called workflow to be reachable by the caller workflow, the | `internal` | `internal`, and `public` | | `public` | `public` | -Additionaly, please note that the **Actions permissions** on the caller's repository Actions settings page must be configured to allow the use of actions and reusable workflows. +The **Actions permissions** on the callers repository's Actions settings page must be configured to allow the use of actions and reusable workflows - see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-select-actions-and-reusable-workflows-to-run)." -Furthermore, except for a public repository, also note that the **Access** policy on the called workflow's repository Actions settings page must be explicitly configured to allow access from repositories in the organization or repositories in the enterprise. +For internal or private repositories, the **Access** policy on the Actions settings page of the called workflow's repository must be explicitly configured to allow access from repositories containing caller workflows. {% data reusables.actions.actions-redirects-workflows %} From ec4b8279003a564145764c713a64aa109010e6c1 Mon Sep 17 00:00:00 2001 From: hubwriter Date: Fri, 24 May 2024 15:50:32 +0100 Subject: [PATCH 6/7] Version "internal" out of FPT docs --- content/actions/using-workflows/reusing-workflows.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 15c1ad53d288..8401f789eea2 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -63,13 +63,13 @@ The following table shows the accessibility of reusable workflows to a caller wo | Caller repository | Accessible workflows repositories | |----|----| -| `private` | `private`, `internal`, and `public` | -| `internal` | `internal`, and `public` | +| `private` | `private`{% ifversion ghes or ghec %}, `internal`,{% endif %} and `public` |{% ifversion ghes or ghec %} +| `internal` | `internal`, and `public` |{% endif %} | `public` | `public` | The **Actions permissions** on the callers repository's Actions settings page must be configured to allow the use of actions and reusable workflows - see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-select-actions-and-reusable-workflows-to-run)." -For internal or private repositories, the **Access** policy on the Actions settings page of the called workflow's repository must be explicitly configured to allow access from repositories containing caller workflows. +For {% ifversion ghes or ghec %}internal or {% endif %}private repositories, the **Access** policy on the Actions settings page of the called workflow's repository must be explicitly configured to allow access from repositories containing caller workflows. {% data reusables.actions.actions-redirects-workflows %} From 69f0f45e9a2f8200924a7f093c131f67578119e8 Mon Sep 17 00:00:00 2001 From: hubwriter Date: Fri, 24 May 2024 16:03:53 +0100 Subject: [PATCH 7/7] Update content/actions/using-workflows/reusing-workflows.md --- content/actions/using-workflows/reusing-workflows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 8401f789eea2..8ee5123d4842 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -69,7 +69,7 @@ The following table shows the accessibility of reusable workflows to a caller wo The **Actions permissions** on the callers repository's Actions settings page must be configured to allow the use of actions and reusable workflows - see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-select-actions-and-reusable-workflows-to-run)." -For {% ifversion ghes or ghec %}internal or {% endif %}private repositories, the **Access** policy on the Actions settings page of the called workflow's repository must be explicitly configured to allow access from repositories containing caller workflows. +For {% ifversion ghes or ghec %}internal or {% endif %}private repositories, the **Access** policy on the Actions settings page of the called workflow's repository must be explicitly configured to allow access from repositories containing caller workflows - see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-a-private-repository)." {% data reusables.actions.actions-redirects-workflows %}