forked from hashicorp/terraform-provider-aws
-
Notifications
You must be signed in to change notification settings - Fork 4
258 lines (225 loc) · 13.1 KB
/
pull_request_target.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
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
name: Process pull_request_target Events
on:
pull_request_target:
types:
- assigned
- closed
- edited
- labeled
- opened
- ready_for_review
jobs:
community_check:
name: 'Community Check'
uses: ./.github/workflows/community-check.yml
secrets: inherit
with:
# This is a ternary that sets the variable to the assigned user's login on assigned events,
# and otherwise sets it to the username of the pull request's author. For more information:
# https://docs.github.com/en/actions/learn-github-actions/expressions#example
username: ${{ github.event.action == 'assigned' && github.event.assignee.login || github.event.pull_request.user.login }}
labeler:
name: 'Automation Labeler'
needs: community_check
runs-on: ubuntu-latest
env:
PR_URL: ${{ github.event.pull_request.html_url }}
steps:
- name: 'Generate Token'
id: token
uses: tibdex/github-app-token@3beb63f4bd073e61482598c45c71c1019b59b73a # v2.1.0
with:
app_id: ${{ secrets.APP_ID }}
installation_retrieval_mode: id
installation_retrieval_payload: ${{ secrets.INSTALLATION_ID }}
private_key: ${{ secrets.APP_PEM }}
- name: 'Add needs-triage for non-maintainers'
if: github.event.action == 'opened' && needs.community_check.outputs.maintainer == 'false'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: gh pr edit ${{ env.PR_URL }} --add-label needs-triage
- name: 'Add prioritized to pull requests authored by or assigned to maintainers'
# This conditional is basically an exact copy of an example provided by GitHub:
# https://docs.github.com/en/actions/learn-github-actions/expressions#example-matching-an-array-of-strings
if: contains(fromJSON('["opened", "assigned"]'), github.event.action) && needs.community_check.outputs.maintainer == 'true'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: gh pr edit ${{ env.PR_URL }} --add-label prioritized
- name: 'Add partner to partner pull requests'
if: github.event.action == 'opened' && needs.community_check.outputs.partner == 'true'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: gh pr edit ${{ env.PR_URL }} --add-label partner
- name: 'Add external-maintainer to external maintainer pull requests'
if: github.event.action == 'opened' && needs.community_check.outputs.core_contributor == 'true'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: gh pr edit ${{ env.PR_URL }} --add-label external-maintainer
- name: 'Add prioritized to regressions'
if: github.event.label.name == 'regression'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: gh pr edit ${{ env.PR_URL }} --add-label prioritized
- name: 'Remove unnecessary labels on closure'
if: github.event.action == 'closed'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: gh pr edit ${{ env.PR_URL }} --remove-label needs-triage,waiting-response
service_labeler:
name: 'Service Labeler'
if: contains(fromJSON('["opened", "edited"]'), github.event.action)
runs-on: ubuntu-latest
steps:
- name: 'Checkout Repo'
uses: actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29 # v4.1.6
- name: 'Apply Labels'
uses: actions/labeler@8558fd74291d67161a8a78ce36a881fa63b766a9 # v5.0.0
with:
configuration-path: .github/labeler-pr-triage.yml
repo-token: ${{ secrets.GITHUB_TOKEN }}
size_labeler:
name: 'Size Labeler'
if: contains(fromJSON('["opened", "edited"]'), github.event.action)
runs-on: ubuntu-latest
steps:
- name: 'Apply Size Labels'
uses: codelytv/pr-size-labeler@56f6f0fc35c7cc0f72963b8467729e1120cb4bed # v1.10.0
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
xs_label: 'size/XS'
xs_max_size: '30'
s_label: 'size/S'
s_max_size: '60'
m_label: 'size/M'
m_max_size: '150'
l_label: 'size/L'
l_max_size: '300'
xl_label: 'size/XL'
message_if_xl: ''
add_to_project:
name: 'Add to Project'
runs-on: ubuntu-latest
needs: community_check
env:
# Some gh project calls take the project's ID, some take the project's number
PROJECT_ID: "PVT_kwDOAAuecM4AF-7h"
PROJECT_NUMBER: "196"
STATUS_FIELD_ID: "PVTSSF_lADOAAuecM4AF-7hzgDcsQA"
VIEW_FIELD_ID: "PVTSSF_lADOAAuecM4AF-7hzgMRB34"
ITEM_URL: ${{ github.event.pull_request.html_url }}
steps:
- name: 'Generate Token'
id: token
uses: tibdex/github-app-token@3beb63f4bd073e61482598c45c71c1019b59b73a # v2.1.0
with:
app_id: ${{ secrets.APP_ID }}
installation_retrieval_mode: id
installation_retrieval_payload: ${{ secrets.INSTALLATION_ID }}
private_key: ${{ secrets.APP_PEM }}
- name: 'Maintainer Pull Requests'
if: github.event.action == 'opened' && needs.community_check.outputs.maintainer == 'true'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: |
# In order to update the item's Status field, we need to capture the project item id from the output
PROJECT_ITEM_ID=$(gh project item-add ${{ env.PROJECT_NUMBER }} --owner "hashicorp" --url ${{ env.ITEM_URL }} --format json | jq '.id')
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.STATUS_FIELD_ID }} --single-select-option-id ${{ vars.team_project_status_maintainer_pr }}
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.VIEW_FIELD_ID }} --single-select-option-id ${{ vars.team_project_view_working_board }}
- name: 'Assigned to Maintainers'
if: github.event.action == 'assigned' && needs.community_check.outputs.maintainer == 'true'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: |
PROJECT_ITEM_ID=$(gh project item-add ${{ env.PROJECT_NUMBER }} --owner "hashicorp" --url ${{ env.ITEM_URL }} --format json | jq '.id')
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.STATUS_FIELD_ID }} --single-select-option-id ${{ vars.team_project_status_in_progress }}
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.VIEW_FIELD_ID }} --single-select-option-id ${{ vars.team_project_view_working_board }}
- name: 'Labeled Prioritized'
if: github.event.label.name == 'prioritized'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: |
PROJECT_ITEM_ID=$(gh project item-add ${{ env.PROJECT_NUMBER }} --owner "hashicorp" --url ${{ env.ITEM_URL }} --format json | jq '.id')
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.VIEW_FIELD_ID }} --single-select-option-id ${{ vars.team_project_view_working_board }}
- name: 'Labeled Regression'
if: github.event.label.name == 'regression'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: |
PROJECT_ITEM_ID=$(gh project item-add ${{ env.PROJECT_NUMBER }} --owner "hashicorp" --url ${{ env.ITEM_URL }} --format json | jq '.id')
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.VIEW_FIELD_ID }} --single-select-option-id ${{ vars.team_project_view_working_board }}
gh api graphql -F itemId="$PROJECT_ITEM_ID" -F projectId=${{ env.PROJECT_ID }} -f query='
mutation($itemId:ID!, $projectId:ID!) {
updateProjectV2ItemPosition(input:{itemId:$itemId, projectId:$projectId}) {
clientMutationId
}
}'
- name: 'Labeled Engineering Initiative'
if: github.event.label.name == 'engineering-initiative'
env:
GH_TOKEN: ${{ steps.token.outputs.token }}
run: |
PROJECT_ITEM_ID=$(gh project item-add ${{ env.PROJECT_NUMBER }} --owner "hashicorp" --url ${{ env.ITEM_URL }} --format json | jq '.id')
gh project item-edit --id "$PROJECT_ITEM_ID" --project-id ${{ env.PROJECT_ID }} --field-id ${{ env.VIEW_FIELD_ID }} --single-select-option-id ${{ vars.team_project_view_engineering_initiative }}
add_to_milestone:
name: 'Add Merged Pull Requests and Related Issues to Milestone'
if: github.event.action == 'closed' && github.event.pull_request.merged
runs-on: ubuntu-latest
steps:
- name: 'Checkout'
uses: actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29 # v4.1.6
- name: 'Get Current Milestone Name'
id: get-current-milestone
run: echo "current_milestone=v$(head -1 CHANGELOG.md | cut -d " " -f 2)" >> "$GITHUB_OUTPUT"
- name: 'Add Items to Milestone'
env:
GH_TOKEN: ${{ github.token }}
MILESTONE: ${{ steps.get-current-milestone.outputs.current_milestone }}
PR_NUMBER: ${{ github.event.pull_request.number }}
shell: bash
run: ./.ci/scripts/add-to-milestone.sh
community_note:
name: 'Community Note'
if: github.event.action == 'opened'
runs-on: ubuntu-latest
steps:
- name: 'Add community note to new Pull Requests'
uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4.0.0
with:
issue-number: ${{ github.event.pull_request.number }}
body: |
# Community Note
**Voting for Prioritization**
* Please vote on this pull request 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 pull 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.
**For Submitters**
* Review the [contribution guide](https://hashicorp.github.io/terraform-provider-aws/) relating to the type of change you are making to ensure all of the necessary steps have been taken.
* For new resources and data sources, use [skaff](https://hashicorp.github.io/terraform-provider-aws/skaff/) to generate scaffolding with comments detailing common expectations.
* Whether or not the branch has been rebased will **not** impact prioritization, but doing so is always a welcome surprise.
first_contribution_note:
name: 'New Contributor Note'
if: github.event.action == 'opened'
runs-on: ubuntu-latest
steps:
- name: 'Add comment to add helpful context for new contributors'
uses: actions/first-interaction@34f15e814fe48ac9312ccf29db4e74fa767cbab7 # v1.3.0
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
pr-message: |-
Welcome @${{github.actor}} :wave:
It looks like this is your first Pull Request submission to the [Terraform AWS Provider](https://github.com/hashicorp/terraform-provider-aws)! If you haven’t already done so please make sure you have checked out our [CONTRIBUTOR](https://hashicorp.github.io/terraform-provider-aws/) guide and [FAQ](https://hashicorp.github.io/terraform-provider-aws/faq/) to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our [FAQ](https://hashicorp.github.io/terraform-provider-aws/faq/) which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! :smiley:
permissions_check:
name: 'Verify Maintainers Editable'
needs: community_check
if: github.event.action == 'opened' && needs.community_check.outputs.maintainer == 'false' && !github.event.pull_request.maintainer_can_modify
runs-on: ubuntu-latest
steps:
- name: 'Comment if maintainers cannot edit'
uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4.0.0
with:
issue-number: ${{ github.event.pull_request.number }}
body: |
Hey @${{ github.actor }} :wave: Thank you very much for your contribution! At times, our maintainers need to make direct edits to pull requests in order to help get it ready to be merged. Your current settings do not allow maintainers to make such edits. To help facilitate this, update your pull request to allow such edits as described in GitHub's [Allowing changes to a pull request branch created from a fork][1] documentation. (If you're using a fork owned by an organization, your organization may not allow you to change this setting. If that is the case, let us know.)
[1]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork