You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/notifier-bot/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ It currently supports:
11
11
- Slack workspace subscriptions
12
12
- npm package polling
13
13
- Multi-channel Slack tracking per workspace
14
+
- Delayed GitHub metadata enrichment and AI release summaries
14
15
15
16
More detailed docs live here:
16
17
@@ -29,6 +30,7 @@ An hourly cron checks tracked packages for updates. When a newer version is foun
29
30
2. GitHub repo metadata is stored on the package when it can be derived from npm metadata.
30
31
3. Matching subscribers are grouped by Slack target channel.
31
32
4. Slack notifications are sent to the relevant channel or the workspace default channel.
33
+
5. If upstream metadata is incomplete, Patch Pulse retries later, updates the original post with release links, and adds an AI summary in the thread when the evidence is strong enough.
32
34
33
35
## Slack Summary
34
36
@@ -61,3 +63,4 @@ Useful commands from this package directory:
61
63
-`/npmlist` does not perform live npm lookups. It uses stored package metadata so the response stays fast.
62
64
- GitHub links in `/npmlist` appear after polling has enriched a package with repo metadata.
63
65
- Update notifications can include richer release links because polling already fetches npm manifests during the update check.
66
+
- Patch Pulse uses status reactions on the original Slack post: `⏳` queued/pending, `📝` summary added, `⚠️` no trustworthy release details found after retries, `❌` processing failed.
0 commit comments