Repository navigation
Replace personal data in the Sentry samples, rename the Baseten async event - #90
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mpleted Baseten's async inference docs now name the webhook event async_predict_completed. The sample is doc-sourced, so rename the file and update its type and topic to match the registry's samples-doc copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Nov 19, 2026
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.
Two separate commits.
Sentry: personal data. Four of the Sentry doc-sourced samples still carried a person's name or a routable IP address from the vendor's example. This swaps them for the same placeholders the webhook-registry uses for these files, so the next sync from
samples-doc/won't reintroduce or churn them.providers/sentry/latest/:installation.created.json:body.actor.nameis nowExample Usercomment.created.json:body.actor.nameis nowExample Usererror.created.json:body.data.error.tags[7][1](theusertag) is nowip:203.0.113.1event_alert.triggered.json:body.data.event.tags[7][1](theusertag) is nowip:203.0.113.1user.ip_addressin the last two files was already203.0.113.2. No other Sentry file holds names, emails or non-documentation IPs. Formatting,index.jsonand provenance are unchanged.Baseten: event rename. Baseten's async inference docs (docs.baseten.co/inference/async) now name the webhook event
async_predict_completed, notasync_request_completed. The version issourced_via: docs, so the sample is renamed rather than kept as a capture:providers/baseten/latest/async_request_completed.jsonis nowasync_predict_completed.jsonbody.typeandtopicare nowasync_predict_completed, andsource.retrievedis2026-11-18providers/baseten/index.json:provenance.latest.sourced_onis2026-11-18, since this is the version's only fileBoth files now match the registry's
samples-doc/providers/baseten/byte for byte.yarn compileandyarn testpass.🤖 Generated with Claude Code