also looking at this
feat(events): one notification story — fire every declared event, trim setup to its real job
#1449
14 files
+308
-81
| @@ -488,6 +488,26 @@ interface NotificationSettings { | ||
| 488 | 488 | Credentials are referenced by environment variable name, never inlined, so a |
| 489 | 489 | destination can be committed without committing its credential. |
| 490 | 490 | |
| 491 | Every event can be named in an `events` filter, and every one of them fires: | |
| 492 | ||
| 493 | | Event | Fired when | | |
| 494 | |-------|-----------| | |
| 495 | | `scan.completed` | a dependency scan finishes, with update counts | | |
| 496 | | `pr.created` | buddy opens a pull request | | |
| 497 | | `pr.updated` | buddy updates or reopens an existing pull request | | |
| 498 | | `pr.closed` | buddy auto-closes a pull request (satisfied, obsolete, or no longer produced by the configuration) | | |
| 499 | | `pr.merged` | buddy auto-merges an eligible pull request | | |
| 500 | | `security.advisories` | a scan flags dependencies with known advisories | | |
| 501 | | `dashboard.updated` | the dependency dashboard issue is created or refreshed | | |
| 502 | | `review.completed` | a pull request review finishes, with the finding count | | |
| 503 | | `gate.failed` | merge gates conclude with a blocking failure | | |
| 504 | | `fixci.completed` | a fix-ci run completes its diagnosis or repair | | |
| 505 | | `run.failed` | a runtime command (scan, update, update-check, dashboard, review, fix-ci) fails | | |
| 506 | ||
| 507 | Webhook consumers receive `{ version, event, payload, sentAt }` JSON. When | |
| 508 | `secretEnv` is set, each request carries an `x-buddy-signature: sha256=<hmac>` | |
| 509 | header signing the raw body. | |
| 510 | ||
| 491 | 511 | ## Pull Requests |
| 492 | 512 | |
| 493 | 513 | ```typescript |