Skip to content

chore: add Sentry license attribution#164

Merged
marandaneto merged 1 commit into
mainfrom
chore/add-sentry-license-attribution
Jun 3, 2026
Merged

chore: add Sentry license attribution#164
marandaneto merged 1 commit into
mainfrom
chore/add-sentry-license-attribution

Conversation

@marandaneto

Copy link
Copy Markdown
Member

💡 Motivation and Context

Add explicit attribution for portions of the codebase derived from getsentry/sentry-ruby and include the relevant Sentry MIT license text in the repository license file.

💚 How did you test it?

  • git diff --check
  • ruby -c posthog-rails/lib/posthog/rails/configuration.rb
  • ruby -c posthog-rails/lib/posthog/rails/parameter_filter.rb
  • ruby -c posthog-rails/lib/posthog/rails/rescued_exception_interceptor.rb

📝 Checklist

  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

If releasing new changes

  • Ran pnpm changeset to generate a changeset file

@marandaneto marandaneto requested a review from a team as a code owner June 3, 2026 10:07
@marandaneto marandaneto requested review from a team, ablaszkiewicz, cat-ph and hpouillot June 3, 2026 10:07
@greptile-apps

greptile-apps Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor
Prompt To Fix All With AI
Fix the following 5 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 5
LICENSE:25-26
The copyright holder name appears to be missing "Functional". Other Sentry SDK repositories (e.g. `sentry-go`) use **"Functional Software, Inc. dba Sentry"** as the full legal entity name. Dropping "Functional" may result in an inaccurate attribution.

```suggestion
Some files in this codebase contain code from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry.
In such cases it is explicitly stated in the file header. This license only applies to the relevant code in such cases.
```

### Issue 2 of 5
LICENSE:30
The copyright year in the Sentry block is 2020, but the sentry-ruby repository was created in 2018 and other Sentry SDK licenses use earlier years. Worth double-checking against the actual `getsentry/sentry-ruby` LICENSE file to ensure the year is accurate.

```suggestion
Copyright (c) 2018 Sentry
```

### Issue 3 of 5
posthog-rails/lib/posthog/rails/configuration.rb:3
Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

```suggestion
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
```

### Issue 4 of 5
posthog-rails/lib/posthog/rails/parameter_filter.rb:3
Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

```suggestion
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
```

### Issue 5 of 5
posthog-rails/lib/posthog/rails/rescued_exception_interceptor.rb:3
Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

```suggestion
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
```

Reviews (1): Last reviewed commit: "chore: add Sentry license attribution" | Re-trigger Greptile

Comment thread LICENSE
Comment on lines +25 to +26
Some files in this codebase contain code from getsentry/sentry-ruby by Software, Inc. dba Sentry.
In such cases it is explicitly stated in the file header. This license only applies to the relevant code in such cases.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 The copyright holder name appears to be missing "Functional". Other Sentry SDK repositories (e.g. sentry-go) use "Functional Software, Inc. dba Sentry" as the full legal entity name. Dropping "Functional" may result in an inaccurate attribution.

Suggested change
Some files in this codebase contain code from getsentry/sentry-ruby by Software, Inc. dba Sentry.
In such cases it is explicitly stated in the file header. This license only applies to the relevant code in such cases.
Some files in this codebase contain code from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry.
In such cases it is explicitly stated in the file header. This license only applies to the relevant code in such cases.
Prompt To Fix With AI
This is a comment left during a code review.
Path: LICENSE
Line: 25-26

Comment:
The copyright holder name appears to be missing "Functional". Other Sentry SDK repositories (e.g. `sentry-go`) use **"Functional Software, Inc. dba Sentry"** as the full legal entity name. Dropping "Functional" may result in an inaccurate attribution.

```suggestion
Some files in this codebase contain code from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry.
In such cases it is explicitly stated in the file header. This license only applies to the relevant code in such cases.
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Comment thread LICENSE

MIT License

Copyright (c) 2020 Sentry

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 The copyright year in the Sentry block is 2020, but the sentry-ruby repository was created in 2018 and other Sentry SDK licenses use earlier years. Worth double-checking against the actual getsentry/sentry-ruby LICENSE file to ensure the year is accurate.

Suggested change
Copyright (c) 2020 Sentry
Copyright (c) 2018 Sentry
Prompt To Fix With AI
This is a comment left during a code review.
Path: LICENSE
Line: 30

Comment:
The copyright year in the Sentry block is 2020, but the sentry-ruby repository was created in 2018 and other Sentry SDK licenses use earlier years. Worth double-checking against the actual `getsentry/sentry-ruby` LICENSE file to ensure the year is accurate.

```suggestion
Copyright (c) 2018 Sentry
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@@ -1,5 +1,8 @@
# frozen_string_literal: true

# Portions of this file are derived from getsentry/sentry-ruby by Software, Inc. dba Sentry

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

Suggested change
# Portions of this file are derived from getsentry/sentry-ruby by Software, Inc. dba Sentry
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
Prompt To Fix With AI
This is a comment left during a code review.
Path: posthog-rails/lib/posthog/rails/configuration.rb
Line: 3

Comment:
Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

```suggestion
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@@ -1,5 +1,8 @@
# frozen_string_literal: true

# Portions of this file are derived from getsentry/sentry-ruby by Software, Inc. dba Sentry

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

Suggested change
# Portions of this file are derived from getsentry/sentry-ruby by Software, Inc. dba Sentry
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
Prompt To Fix With AI
This is a comment left during a code review.
Path: posthog-rails/lib/posthog/rails/parameter_filter.rb
Line: 3

Comment:
Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

```suggestion
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@@ -1,5 +1,8 @@
# frozen_string_literal: true

# Portions of this file are derived from getsentry/sentry-ruby by Software, Inc. dba Sentry

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

Suggested change
# Portions of this file are derived from getsentry/sentry-ruby by Software, Inc. dba Sentry
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
Prompt To Fix With AI
This is a comment left during a code review.
Path: posthog-rails/lib/posthog/rails/rescued_exception_interceptor.rb
Line: 3

Comment:
Same company name issue as in the LICENSE file — "Functional" appears to be missing from the attribution.

```suggestion
# Portions of this file are derived from getsentry/sentry-ruby by Functional Software, Inc. dba Sentry
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@marandaneto marandaneto merged commit 7f0afe4 into main Jun 3, 2026
20 checks passed
@marandaneto marandaneto deleted the chore/add-sentry-license-attribution branch June 3, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants