Replace cURL to Slack with slackapi/slack-github-action
#3461
Labels
🤖 aspect: dx
Concerns developers' experience with the codebase
✨ goal: improvement
Improvement to an existing user-facing feature
good first issue
New-contributor friendly
help wanted
Open to participation from the community
🟩 priority: low
Low priority and doesn't need to be rushed
🧱 stack: mgmt
Related to repo management and automations
🔧 tech: github actions
Involves Github Actions
Problem
The following workflows make Slack API calls using a cURL request.
openverse/.github/workflows/discussion_ping.yml
Lines 23 to 27 in c312886
openverse/.github/workflows/pr_limit_reminders.yml
Lines 38 to 47 in c312886
openverse/.github/workflows/pr_ping.yml
Lines 31 to 35 in c312886
openverse/.github/workflows/pr_ping.yml
Lines 40 to 44 in c312886
Description
A better approach is to use the (official?) Slack API action
slackapi/slack-github-action@v1.23.0
by means of technique 3 i.e. incoming webhooks. These workflows can be coverted to that actions making them more maintainable because cURL and Bash (and especially together) can be notoriously hard to understand and make changes to.The text was updated successfully, but these errors were encountered: