Files
charts/.github/workflows/move-closed-issues.yml
Alejandro Gómez Morón 413206a72d Parametrizing support flow by using GH teams and fixing and fixing an issue with comments (#11355)
* Parametrizing support flow by getting GH members from GH teams. Also changing personal token into bitnami-bot one

Signed-off-by: Alejandro Gómez <morona@vmware.com>

* Changing token to retrieve team members since the rate limiting for bitnami-bot was fixed

Signed-off-by: Alejandro Gómez <morona@vmware.com>

* Changing token to retrieve team members since the rate limiting for bitnami-bot was fixed

Signed-off-by: Alejandro Gómez <morona@vmware.com>

* Changing finally when it's executed, not the token

Signed-off-by: Alejandro Gómez <morona@vmware.com>

* After checking with @fmulero, for org teams we need the bitnami-bot token

Signed-off-by: Alejandro Gómez <morona@vmware.com>
2022-07-29 11:31:55 +02:00

46 lines
1.3 KiB
YAML

name: '[Support] Move closed issues'
on:
issues:
types:
- closed
pull_request_target:
types:
- closed
permissions:
issues: write
repository-projects: write
# To fix the concurrency when for example more than one label is added
concurrency:
group: ${{ github.run_id }}
cancel-in-progress: false
jobs:
send_to_solved:
if: ${{ github.actor != 'bitnami-bot' }}
runs-on: ubuntu-latest
steps:
- name: Repo checkout
uses: actions/checkout@v3
with:
fetch-depth: 1
- name: Load .env file
uses: xom9ikk/dotenv@v1.0.2
with:
path: .github/workflows/
- name: Send to the Solved column
uses: peter-evans/create-or-update-project-card@v2
with:
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"