-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
199 lines (166 loc) · 10 KB
/
issues_handleLabel.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
name: Issue Labeled
on:
issues:
types: [labeled]
permissions:
issues: write
pull-requests: write
actions: read
checks: read
contents: read
repository-projects: read
statuses: read
jobs:
issue-labeled:
runs-on: ubuntu-latest
steps:
# Unable to Reproduce Tasks
- name: 'Comment: unable to reproduce'
if: "${{ github.event.label.name == 'status: can not reproduce' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'create-comment'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
> This is a templated message
Hello @${{ github.event.issue.user.login }},
Thank you for reporting this bug, however we are unable to reproduce the issue you described given the information we have on hand. Can you please create a fresh project that you are able to reproduce the issue in, provide clear steps to reproduce this issue, and either upload this fresh project to a new GitHub repo or compress it into a `.zip` and upload it on this issue?
We would greatly appreciate your assistance with this, by working in a fresh project it will cut out any possible variables that might be unrelated.
Please note that issues labeled with `status: can not reproduce` will be closed in 14 days if there is no activity.
Thank you!
# Support team auto assign
- name: 'Assign: add random solution engineer to reproduction issues'
if: "${{ github.event.label.name == 'status: pending reproduction' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'add-assignees'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
assignees: 'derrickmehaffy, kasonde, bolg55, Eventyret, dennism501, n-alonso'
random-to: 1
# v3 Legacy Issues
- name: 'Comment: unsupported v3 issues'
if: "${{ github.event.label.name == 'flag: v3-unsupported' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'create-comment'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
> This is a templated message
Hello @${{ github.event.issue.user.login }},
Thank you for reporting this potential bug report, please keep in mind that we are no longer accepting bug reports for Strapi v3.
The recommended action we suggest for v3 users is to utilize the various migration resources to upgrade your package from Strapi v3 to Strapi v4:
- [Code Migration Guide](https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/v4/code-migration.html) and/or [Codemods project](https://github.com/strapi/codemods)
- [Data Migration Guide](https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/v4/data-migration.html) and/or [Data Migration Scripts](https://github.com/strapi/migration-scripts)
- [Plugin Migration Guide](https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/v4/plugin-migration.html)
Please see our [Security file](https://github.com/strapi/strapi/security) for more information about supported versions.
For now this issue is marked as closed.
Thank You
- name: 'Close: unsupported v3 issues'
if: "${{ github.event.label.name == 'flag: v3-unsupported' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'close-issue'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
close-reason: 'not_planned'
# Feature request redirections
- name: 'Comment: redirect feature request to canny'
if: "${{ github.event.label.name == 'issue: feature request' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'create-comment'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
> This is a templated message
Hello @${{ github.event.issue.user.login }},
First thank you for reporting this feature need.
To manage feature requests and the Strapi roadmap, we are using Canny.
You will be able to access the Public Roadmap here: https://feedback.strapi.io.
In your message, please mention the URL of this thread in case some messages are posted there. But the most important is to have your feedback posted on our feedback/roadmap site.
The product team is reading EVERY comment, that really helps us to develop the project in the right direction. We are keeping all feature requests and project insights in one place, our feedback website.
In order to keep our GitHub issues clean and for valid bug reports this issue will be marked as closed, but please feel free to continue the discussion with other community members here.
Thank you for your insight and have a good day.
- name: 'Close: redirect feature request to canny'
if: "${{ github.event.label.name == 'issue: feature request' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'close-issue'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
close-reason: 'completed'
# Invalid bug report template actions
- name: 'Comment: invalid bug report template'
if: "${{ github.event.label.name == 'flag: invalid template' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'create-comment'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
> This is a templated message
Hello @${{ github.event.issue.user.login }},
We ask that you please follow the [issue template](https://raw.githubusercontent.com/strapi/strapi/master/.github/ISSUE_TEMPLATE/BUG_REPORT.md).
A proper issue submission let's us better understand the origin of your bug and therefore help you. We will reopen your issue when we receive the issue following the template guidelines and properly fill out the template. You can see the template guidelines for bug reports [here](https://github.com/strapi/strapi/blob/master/CONTRIBUTING.md#reporting-an-issue).
Please update the issue with the template and we can reopen this report.
Thank you.
- name: 'Close: invalid bug report template'
if: "${{ github.event.label.name == 'flag: invalid template' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'close-issue'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
close-reason: 'not_planned'
# Redirect questions to community sources
- name: 'Comment: redirect question to community'
if: "${{ github.event.label.name == 'flag: question' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'create-comment'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
> This is a templated message
Hello @${{ github.event.issue.user.login }},
I see you are wanting to ask a question that is not really a bug report,
- questions should be directed to [our forum](https://forum.strapi.io) or our [Discord](https://discord.strapi.io)
- feature requests should be directed to our [feedback and feature request database](https://feedback.strapi.io)
Please see the following contributing guidelines for asking a question [here](https://github.com/strapi/strapi/blob/master/CONTRIBUTING.md#reporting-an-issue).
Thank you.
- name: 'Close: redirect question to community'
if: "${{ github.event.label.name == 'flag: question' }}"
uses: actions-cool/issues-helper@v3
with:
actions: 'close-issue'
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
close-reason: 'complete'
# Critical issue alerting
# - name: alert team to critical issue
# if: "${{ github.event.label.name == 'severity: critical' }}"
# uses: rtCamp/action-slack-notify@v2
# env:
# SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
# SLACK_CHANNEL: crisis
# SLACK_COLOR: bad
# SLACK_TITLE: Issue marked as Critical!
# SLACK_USERNAME: Strapi-Alerts
# SLACK_FOOTER: Triggered by GitHub Actions
- name: assign issues to DevExp squad project
uses: actions/add-to-project@v0.4.1
with:
project-url: https://github.com/orgs/strapi/projects/13
github-token: ${{ secrets.PROJECT_TRANSFER_TOKEN }}
labeled: 'source: cli, source: core:content-type-builder, source: core:core, source: core:data-transfer, source: core:database, source: core:strapi, source: core:utils, source: dependencies, source: docs, source: external, source: generators:app, source: generators, source: marketplace, source: plugin:graphql, source: plugin:users-permissions, source: tooling, source: typescript, source: utils:pack-up, source: utils:upgrade'
label-operator: OR
- name: assign issues to Content squad project
uses: actions/add-to-project@v0.4.1
with:
project-url: https://github.com/orgs/strapi/projects/23
github-token: ${{ secrets.PROJECT_TRANSFER_TOKEN }}
labeled: 'source: core:admin, source: core:content-manager, source: core:content-releases, source: core:email, source: core:helper-plugin, source: core:permissions, source: core:review-workflows, source: core:upload, source: plugin:cloud, source: plugin:color-picker, source: plugin:documentation, source: , plugin:i18n, source: plugin:sentry, source: providers'
label-operator: OR