fix: nest handler spans under webhook transaction #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/nest-handler-spans"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
HandleRepositoryCreated/Deleted were creating separate top-level
transactions instead of child spans under the webhook transaction.
Changed startTransaction to startSpan so the handler operations
(get_user, create_user, etc.) appear as child spans in GlitchTip.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Automated review by pr-reviewer v0.15.0 | Safety Check | anthropic | tracking id
r-c489d0-096942This is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — The changes properly convert top-level transactions to child spans for better tracing hierarchy without introducing any obvious bugs or security issues.
Complexity: trivial
The diff shows a straightforward refactoring to improve tracing structure by changing
startTransactiontostartSpancalls. The change maintains the same error handling and defer patterns while properly nesting spans under the webhook transaction. No security vulnerabilities or obvious bugs are present. The variable renaming fromtxCtx/txtohandlerCtx/handlerSpanis consistent throughout and the function signatures remain unchanged.