Use GITHUB_TOKEN instead of BITNAMI_BOT to label issues and PRs (#12257)

Signed-off-by: Fran Mulero <fmulero@vmware.com>

Signed-off-by: Fran Mulero <fmulero@vmware.com>

.github/workflows/clossing-issues.yml

@@ -6,6 +6,7 @@ on:
 
 permissions:
   issues: write
+  pull-requests: write
   repository-projects: write
 
 jobs:

.github/workflows/comments.yml

@@ -4,8 +4,9 @@ on:
     types:
       - created
 permissions:
-  repository-projects: write
   issues: write
+  pull-requests: write
+  repository-projects: write
 
 # To fix the concurrency when for example more than one label is added
 concurrency:

.github/workflows/move-closed-issues.yml

@@ -9,6 +9,7 @@ on:
 
 permissions:
   issues: write
+  pull-requests: write
   repository-projects: write
 
 # To fix the concurrency when for example more than one label is added
@@ -35,12 +36,10 @@ jobs:
           project-name: Support
           # If the author comes from Bitnami, send it to Bitnami. Otherwise, all to Triage
           column-name: 'Solved'
-          token: "${{ secrets.BITNAMI_BOT_TOKEN }}"
           issue-number: ${{ github.event_name != 'issues' && github.event.number || github.event.issue.number }}
       - name: Solved labeling
         # Only if moved into Solved
         uses: andymckay/labeler@1.0.4
         with:
-          repo-token: "${{ secrets.BITNAMI_BOT_TOKEN }}"
           add-labels: "solved"
           remove-labels: "in-progress, on-hold, triage"

.github/workflows/moving-cards.yml

@@ -6,8 +6,9 @@ on:
       - moved
 
 permissions:
-  repository-projects: read
   issues: write
+  pull-requests: write
+  repository-projects: read
 
 # To fix the concurrency when for example more than one label is added
 concurrency:
@@ -33,7 +34,6 @@ jobs:
         if: ${{ github.event.project_card.column_id == env.ON_HOLD_COLUMN_ID  }}
         uses: andymckay/labeler@1.0.4
         with:
-          repo-token: "${{ secrets.BITNAMI_BOT_TOKEN }}"
           add-labels: "on-hold"
           remove-labels: "triage"
       - name: In progress labeling
@@ -41,7 +41,6 @@ jobs:
         if: ${{ github.event.project_card.column_id == env.IN_PROGRESS_COLUMN_ID  }}
         uses: andymckay/labeler@1.0.4
         with:
-          repo-token: "${{ secrets.BITNAMI_BOT_TOKEN }}"
           add-labels: "in-progress"
           remove-labels: "on-hold, triage"
       - name: Solved labeling
@@ -49,7 +48,6 @@ jobs:
         if: ${{ github.event.project_card.column_id == env.SOLVED_COLUMN_ID  }}
         uses: andymckay/labeler@1.0.4
         with:
-          repo-token: "${{ secrets.BITNAMI_BOT_TOKEN }}"
           add-labels: "solved"
           remove-labels: "in-progress, on-hold, triage"
   assign-assignee-if-needed:

.github/workflows/triage.yml

@@ -10,8 +10,9 @@ on:
       - reopened
       - opened
 permissions:
-  repository-projects: write
   issues: write
+  pull-requests: write
+  repository-projects: write
 
 # To fix the concurrency when for example more than one label is added
 concurrency:
@@ -52,7 +53,6 @@ jobs:
         # Only if moved into Solved
         uses: andymckay/labeler@1.0.4
         with:
-          repo-token: "${{ secrets.BITNAMI_BOT_TOKEN }}"
           add-labels: ${{ (!contains(fromJson(env.BITNAMI_TEAM), github.actor)) && 'triage' || 'bitnami' }}
           # For reopened issues
           remove-labels: "solved"