muhdaizwan opened a new issue, #5405:
URL: https://github.com/apache/couchdb/issues/5405

   <!-- MODIFIED_CONTENT_LINKING_COMMENT -->
   ## Automatically generated comment ℹ️
   **This comment is automatically generated and will be overwritten every time 
changes are committed to this branch.**
   
   The table contains an overview of files in the `content` directory that have 
been changed in this pull request. It's provided to make it easy to review your 
changes on the staging site. Please note that changes to the `data` directory 
will not show up in this table.
   
   ---
   
   ### Content directory changes
   _You may find it useful to copy this table into the pull request summary. 
There you can edit it to share links to important articles or changes and to 
give a high-level overview of how the changes in your pull request support the 
overall goals of the pull request._
   | **Source** | **Preview** | **Production** | **What Changed** |
   | :--- | :--- | :--- | :--- |
   | 
[`actions/security-for-github-actions/security-guides/automatic-token-authentication.md`](https://github.com/github/docs/blob/a8aefd2e008380cc6b581da8c7dfd11e6bca5caf/content%2Factions%2Fsecurity-for-github-actions%2Fsecurity-guides%2Fautomatic-token-authentication.md)
 | 
[fpt](https://docs-35967-3dcd32.preview.ghdocs.com/actions/security-for-github-actions/security-guides/automatic-token-authentication)<br>[ghec](https://docs-35967-3dcd32.preview.ghdocs.com/enterprise-cloud@latest/actions/security-for-github-actions/security-guides/automatic-token-authentication)<br>ghes@
 
[3.15](https://docs-35967-3dcd32.preview.ghdocs.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.14](https://docs-35967-3dcd32.preview.ghdocs.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.13](https://docs-35967-3dcd32.preview.ghdocs.com/[email protected]/actions/security-for-
 github-actions/security-guides/automatic-token-authentication) 
[3.12](https://docs-35967-3dcd32.preview.ghdocs.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.11](https://docs-35967-3dcd32.preview.ghdocs.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.10](https://docs-35967-3dcd32.preview.ghdocs.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 <br> | 
[fpt](https://docs.github.com/actions/security-for-github-actions/security-guides/automatic-token-authentication)<br>[ghec](https://docs.github.com/enterprise-cloud@latest/actions/security-for-github-actions/security-guides/automatic-token-authentication)<br>ghes@
 
[3.15](https://docs.github.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 [3.14](https://docs.github.com/enterprise-serve
 
[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.13](https://docs.github.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.12](https://docs.github.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.11](https://docs.github.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 
[3.10](https://docs.github.com/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication)
 <br> |  |
   
   
   ---
   fpt: Free, Pro, Team
   ghec: GitHub Enterprise Cloud
   ghes: GitHub Enterprise Server
   
   _Originally posted by @github-actions in 
https://github.com/github/docs/pull/35967#issuecomment-2596305220_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to