Merge branch 'layer5io:master' into master

Author: kishore08-07

.github/workflows/label-triggered.yml

@@ -38,7 +38,7 @@ jobs:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           comment: "We are sending you an invitation to join the Layer5 GitHub Organization. :partying_face: <b>Welcome to the community! 🎉</b><br /><br />&nbsp;&nbsp;&nbsp;Be sure to :star: [star the projects](../stargazers), if you haven't already.<br />"
         env:
-          INVITE_TOKEN: ${{ secrets.RELEASEDRAFTER_PAT }}
+          INVITE_TOKEN: ${{ secrets.GH_ACCESS_TOKEN }}
       - name: View context attributes
         uses: actions/github-script@master
         id: set-url

src/collections/handbook/github-process/index.mdx

@@ -41,8 +41,6 @@ Layer5 has the following org-wide secrets available:
       <tr><td>DOCKER_USERNAME</td><td>"mesheryci"</td></tr>
       <tr><td>NETLIFY_AUTH_TOKEN</td><td>Netlify authentication token used for deployment.</td></tr>
       <tr><td>NETLIFY_SITE_ID</td><td>Unique ID of the Netlify site to deploy to.</td></tr>
-      <tr><td>RELEASEDRAFTER_PAT</td><td>Belongs to user "l5io"</td></tr>
-      <tr><td>RELEASE_NOTES_PAT</td><td>Belongs to user "l5io"</td></tr>
       <tr><td>SLACK_BOT_TOKEN</td><td>Authentication token for the Slack bot integration.</td></tr>
       <tr><td>GITHUB_TOKEN</td><td>For the community scope repo that can be use commit and release</td></tr>
       <tr><td>NODE_VERSION</td><td>"v18" as of Nov 15, 2022.</td></tr>
@@ -51,10 +49,6 @@ Layer5 has the following org-wide secrets available:
       <tr><td>NPM_TOKEN</td><td>l5io user's token for publishing packages</td></tr>
       <tr><td>INTEGRATION_SPREADSHEET_CRED</td><td>Base64 encoded cred for accessing integration spreadsheet on behalf of user  <a href="mailto: no-reply@layer5.io">no-reply@layer5.io</a></td></tr>
       <tr><td>PLAYGROUND_CONFIG</td><td>Base64 encoded kubeconfig of Playground</td></tr>
-      <tr><td>METAL_SSH_KEY</td><td>SMP Project-wide SSH private key</td></tr>
-      <tr><td>METAL_AUTH_TOKEN</td><td>Metal cli auth token</td></tr>
-      <tr><td>METAL_SERVER1</td><td>ID of 1st metal server running playground</td></tr>
-      <tr><td>METAL_SERVER2</td><td>ID of 2nd metal server running playground</td></tr>
     </tbody>
   </table>
 </div>