-
Notifications
You must be signed in to change notification settings - Fork 9.3k
155 lines (135 loc) · 6.15 KB
/
issues.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
name: "Process issues Events"
on:
issues:
types:
- assigned
- closed
- edited
- opened
- labeled
jobs:
labels:
name: Labelers
runs-on: ubuntu-latest
permissions:
contents: read
issues: write
steps:
- name: Checkout
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
sparse-checkout: .github
- name: Apply Service Labels
if: contains(fromJSON('["opened", "edited"]'), github.event.action)
uses: github/issue-labeler@c1b0f9f52a63158c4adc09425e858e87b32e9685 # v3.4
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
configuration-path: .github/labeler-issue-triage.yml
enable-versioned-regex: 0
include-title: 1
- name: Run Community Check
id: community_check
uses: ./.github/actions/community_check
with:
user_login: ${{ github.event.action == 'assigned' && github.event.assignee.login || github.event.issue.user.login }}
maintainers: ${{ secrets.MAINTAINERS }}
- name: Add needs-triage to New Issues
if: |
github.event.action == 'opened'
&& steps.community_check.outputs.maintainer == 'false'
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: gh issue edit ${{ github.event.issue.html_url }} --add-label needs-triage
- name: Add prioritized When Assigned to a Maintainer
if: |
github.event.action == 'assigned'
&& steps.community_check.outputs.maintainer == 'true'
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: gh issue edit ${{ github.event.issue.html_url }} --add-label prioritized
- name: Remove Triage labels on Closure
if: |
github.event.action == 'closed'
&& (contains(github.event.issue.labels.*.name, 'needs-triage') || contains(github.event.issue.labels.*.name, 'waiting-response'))
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: gh issue edit ${{ github.event.issue.html_url }} --remove-label needs-triage,waiting-response
project:
name: Maintainer Work Board
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- name: Generate GitHub App Token
id: token
uses: actions/create-github-app-token@c1a285145b9d317df6ced56c09f525b5c2b6f755 # v1.11.1
with:
app-id: ${{ secrets.APP_ID }}
private-key: ${{ secrets.APP_PEM }}
- name: Checkout
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
sparse-checkout: .github/actions/
- name: Run Community Check
id: community_check
if: github.event.action == 'assigned'
uses: ./.github/actions/community_check
with:
user_login: ${{ github.event.assignee.login }}
maintainers: ${{ secrets.MAINTAINERS }}
- name: Add Maintainer Assignments
if: |
github.event.action == 'assigned'
&& steps.community_check.outputs.maintainer == 'true'
uses: ./.github/actions/team_working_board
with:
github_token: ${{ steps.token.outputs.token }}
item_url: ${{ github.event.issue.html_url }}
status: "In Progress"
view: "working-board"
- name: Add Issues Labeled prioritized
if: github.event.label.name == 'prioritized'
uses: ./.github/actions/team_working_board
with:
github_token: ${{ steps.token.outputs.token }}
item_url: ${{ github.event.issue.html_url }}
view: "working-board"
- name: Add Issues Labeled engineering-initiative
if: github.event.label.name == 'engineering-initiative'
uses: ./.github/actions/team_working_board
with:
github_token: ${{ steps.token.outputs.token }}
item_url: ${{ github.event.issue.html_url }}
view: "engineering-initiative"
community_note:
name: "Add Community Note"
if: github.event.action == 'opened'
runs-on: ubuntu-latest
steps:
- name: "Add community note to new Issues"
uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4.0.0
with:
issue-number: ${{ github.event.issue.number }}
body: |
# Community Note
**Voting for Prioritization**
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original post to help the community and maintainers prioritize this request.
* Please see our [prioritization guide](https://hashicorp.github.io/terraform-provider-aws/prioritization/) for information on how we prioritize.
* Please **do not** leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
**Volunteering to Work on This Issue**
* If you are interested in working on this issue, please leave a comment.
* If this would be your first contribution, please review the [contribution guide](https://hashicorp.github.io/terraform-provider-aws/).
closed_issue_comment:
name: "Closed Issue Comment"
if: github.event.action == 'closed'
runs-on: ubuntu-latest
steps:
- name: "Add comment on closed issues"
uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4.0.0
with:
issue-number: ${{ github.event.issue.number }}
body: |
> [!WARNING]
> This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
>
> Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the [AWS Provider forum](https://discuss.hashicorp.com/c/terraform-providers/tf-aws/33), is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.