chore: Correct Sentry Python attribution#646
Merged
Merged
Conversation
Contributor
|
Reviews (1): Last reviewed commit: "chore: correct Sentry attribution" | Re-trigger Greptile |
Contributor
posthog-python Compliance ReportDate: 2026-06-03 10:06:42 UTC ✅ All Tests Passed!45/45 tests passed Capture Tests✅ 29/29 tests passed View Details
Feature_Flags Tests✅ 16/16 tests passed View Details
|
cat-ph
approved these changes
Jun 3, 2026
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.
💡 Motivation and Context
The exception capture files are copied/adapted from
getsentry/sentry-python, but the license attribution referencedgetsentry/sentry-javascript. This corrects the source attribution in the file headers and bundled license notice.💚 How did you test it?
Not run (license/header text-only change).
📝 Checklist
If releasing new changes
sampo addto generate a changeset file