ci: dedup upstream API change notifications by UTC day#197
Merged
Conversation
Receiver workflow now folds all repository_dispatch events of type `upstream-api-endpoint-change` arriving on the same UTC day into a single rolling issue titled "Docs review: upstream API changes (YYYY-MM-DD)". Subsequent dispatches that day append a comment instead of opening a duplicate. The previous logic opened one fresh issue per dispatch. Between Feb 18 and Mar 19, 2026 the legacy Mlaz-code/sharp-api dispatcher fired 185 times (peak 30/day on Mar 6). None were ever triaged. Bulk-close of those issues is happening alongside this rewire; the new dispatcher lives in Mlaz-code/sharp-api-go (notify-docs.yml, separate PR).
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Mlaz-code
added a commit
that referenced
this pull request
May 7, 2026
Receiver workflow now folds all repository_dispatch events of type `upstream-api-endpoint-change` arriving on the same UTC day into a single rolling issue titled "Docs review: upstream API changes (YYYY-MM-DD)". Subsequent dispatches that day append a comment instead of opening a duplicate. The previous logic opened one fresh issue per dispatch. Between Feb 18 and Mar 19, 2026 the legacy Mlaz-code/sharp-api dispatcher fired 185 times (peak 30/day on Mar 6). None were ever triaged. Bulk-close of those issues is happening alongside this rewire; the new dispatcher lives in Mlaz-code/sharp-api-go (notify-docs.yml, separate PR).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the per-dispatch
gh issue createin.github/workflows/upstream-notify.ymlwith an upsert: same-UTC-day dispatches fold into a single rolling issue titledDocs review: upstream API changes (YYYY-MM-DD). Subsequent same-day dispatches append a comment to that issue instead of opening a duplicate.The previous one-issue-per-dispatch logic produced 185 unread tickets between Feb 18 and Mar 19, 2026, peaking at 30/day on Mar 6. The legacy dispatcher in
Mlaz-code/sharp-api(TS Hono) was retired with that repo's rewrite to Go; the replacement dispatcher lives inMlaz-code/sharp-api-go(companion PR #154 there).Behavior
Docs review: upstream API changes (YYYY-MM-DD)(UTC).--label upstream+ exact title match against open issues.commit hash→ source repo → changed files).Dependencies
Test plan
repository_dispatchfromsharp-api-goopens a fresh "Docs review" issuehttps://github.com/Mlaz-code/sharp-api-go/commit/<sha>🤖 Generated with Claude Code