Repository navigation
Bring in the registry's later edits to 360 existing doc samples - #94
Merged
Merged
Conversation
204 doc samples across 53 providers changed in webhook-registry after they were exported here (hub preparation PRs #137, #141, #144, #154, #156, #166, #169, #171), so Inspect still showed the older bodies. Each file is a three-way merge against the version first exported here: leaves only the registry changed take the registry's value, leaves only this repo changed keep this repo's (the PII scrubs from #82 to #90), a deletion on either side wins, and where both changed the same leaf this repo's scrubbed value stays. No capture is touched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mp6yzxrVELJ8wYUxdn1aRi
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Review found the leaf-level merge mixed the two trees badly: Aimfox names reverted beside scrubbed emails, Honeybadger's removed second user and Coterie's AdditionalInsureds came back, Middesk kept a half-scrubbed address, and source blocks kept old retrieved dates and urls. So every doc sample the registry changed after export now takes the registry's file whole (headers, body, topic and source): 360 files across 80 providers. Aimfox is left as this repo has it, because the registry's copy still carries real-looking names (registry#193 takes this repo's version instead). Paystack charge.success keeps customer@example.com, and 19 files get the same email placeholders as the registry, sparing Azure DevOps remotes and Mailgun's sample domain. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mp6yzxrVELJ8wYUxdn1aRi
This branch was successfully deployed
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
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.
Requested by Gareth · project thread
Why
#93 only added files. For 360 existing doc samples across 80 providers, webhook-registry rewrote the file after it was exported here, in its hub-prep PRs (hookdeck/webhook-registry#137, #141, #144, #154, #156, #166, #169, #171). Inspect still sends the older versions while the hub shows the new ones. Examples: Zendesk, Unit, Honeybadger, Nium, and Xendit
refund.succeeded.What changes
source, so the retrieved date and URL match the body. In most of these files this repo also scrubbed values. The registry's hub-prep PRs replaced the same values with their own placeholders, so the registry's version is used as it is.charge.successkeepscustomer@example.com. In 19 files, emails outside reserved domains becomeuserN@example.com(AgentMail, Bitdefender, Missive, Slack, Zendesk, and Mailgun message ids and recipients). Azure DevOps git remotes and Mailgun'ssample.mailgun.comaddresses are left as they are. The registry gets the same placeholders in #193.sourcekey are touched, so no capture changes.An earlier commit on this branch merged leaf by leaf instead. Review found that it mixed the two trees: Aimfox names came back next to scrubbed emails, rows the registry had removed reappeared, and source blocks went stale. The second commit replaces that merge.
yarn compileandyarn testpass (26/26).https://claude.ai/code/session_01Mp6yzxrVELJ8wYUxdn1aRi
Generated by Claude Code