Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filter out in-app frames when matching for CODEOWNERS #75588

Merged
merged 8 commits into from
Aug 13, 2024

Conversation

alxckn
Copy link
Contributor

@alxckn alxckn commented Aug 5, 2024

In the documentation for ownership rules, about CODEOWNERS file evaluation on an event's frames, it is stated that "Sentry evaluates an event’s in-app frames against the rules".

As discussed in this issue, this does not seem to be in fact the case (see this comment with a reproduction scenario specifically).

This PR proposes changes to ensure the clause is respected for CODEOWNERS matchers. When matching frames, if they are explicitely not in app (frame.get("in_app" == False), they will be ignored.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Aug 5, 2024
@alxckn alxckn force-pushed the codeowners_on_in_app_frames_only branch from f2f8f61 to 82b3bbf Compare August 6, 2024 09:36
@alxckn alxckn force-pushed the codeowners_on_in_app_frames_only branch from 82b3bbf to ddd2d10 Compare August 7, 2024 13:52
@alxckn alxckn marked this pull request as ready for review August 7, 2024 14:32
@alxckn alxckn requested a review from a team as a code owner August 7, 2024 14:32
@JoshFerge JoshFerge added the Trigger: getsentry tests once code is reviewed: apply label to PR to trigger getsentry tests label Aug 13, 2024
fix type of func
@github-actions github-actions bot removed the Trigger: getsentry tests once code is reviewed: apply label to PR to trigger getsentry tests label Aug 13, 2024
@JoshFerge JoshFerge added the Trigger: getsentry tests once code is reviewed: apply label to PR to trigger getsentry tests label Aug 13, 2024
@JoshFerge
Copy link
Member

thank you for the contribution @alxckn! this change looks good to me. I added one test case and will go ahead and merge after CI passes!

@JoshFerge JoshFerge enabled auto-merge (squash) August 13, 2024 22:03
@JoshFerge JoshFerge merged commit b4bd0df into getsentry:master Aug 13, 2024
47 of 49 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Aug 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components Trigger: getsentry tests once code is reviewed: apply label to PR to trigger getsentry tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants