Repository navigation
docs(webhook): describe the package as using webhooks on the Slack Platform - #2858
Conversation
…atform Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2858 +/- ##
==========================================
+ Coverage 94.25% 94.47% +0.22%
==========================================
Files 67 67
Lines 10808 10808
Branches 680 683 +3
==========================================
+ Hits 10187 10211 +24
+ Misses 590 570 -20
+ Partials 31 27 -4
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
| "name": "@slack/webhook", | ||
| "version": "8.0.2", | ||
| "description": "Official library for using the Slack Platform's Incoming Webhooks", | ||
| "description": "Official library for using webhooks on the Slack Platform", |
There was a problem hiding this comment.
suggestion (non-blocking): The @slack/webhook rows in AGENTS.md and the root README.md still describe it as Incoming Webhooks only. Could be a quick follow-up so they match this.
|
🌟 Thanks for the kind review @mwbrooks! |
Summary
This pull request updates the
@slack/webhookpackage description to cover both kinds of webhook it sends to, since the package has helpers for Incoming Webhooks and Workflow Builder webhook triggers:The new description shows on npm with the next
@slack/webhookrelease.Requirements
🤖 Generated with Claude Code