Skip to content

feat(preprod): Register feature flag and project option for snapshot PR comments#112100

Merged
runningcode merged 2 commits intomasterfrom
no/eme-999-snapshot-pr-comments-flag
Apr 2, 2026
Merged

feat(preprod): Register feature flag and project option for snapshot PR comments#112100
runningcode merged 2 commits intomasterfrom
no/eme-999-snapshot-pr-comments-flag

Conversation

@runningcode
Copy link
Copy Markdown
Contributor

Register the infrastructure needed to gate snapshot PR comments:

  • Feature flag: organizations:preprod-snapshot-pr-comments (FlagPole, api_expose=True)
  • Project option: sentry:preprod_snapshot_pr_comments_enabled (default true)
  • Serializer field and PUT handler in project details endpoint so the toggle is read/writable via the API

This is the first step toward EME-999 — adding PR comment support for snapshot comparisons. Follow-up PRs will add the task, template, frontend toggle, and trigger wiring.

Refs EME-999

…PR comments

Add the infrastructure needed to gate snapshot PR comments:
- Feature flag: organizations:preprod-snapshot-pr-comments
- Project option: sentry:preprod_snapshot_pr_comments_enabled (default true)
- Serializer field and PUT handler in project details endpoint

Refs EME-999
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@linear-code
Copy link
Copy Markdown

linear-code bot commented Apr 2, 2026

EME-999 PR comments

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 2, 2026
@runningcode runningcode marked this pull request as ready for review April 2, 2026 14:03
@runningcode runningcode requested a review from a team as a code owner April 2, 2026 14:03
@shellmayr
Copy link
Copy Markdown
Member

Not aware of the general approach here, so forgive me if this is obvious from context, but I wonder why we need both an org feature flag and and project option? Once GAd, will there be an option to turn this on/off on a per project basis

@runningcode
Copy link
Copy Markdown
Contributor Author

runningcode commented Apr 2, 2026

Good question, yes exactly, once GA, we will allow an option to turn this on/off an a per project basis with a settings toggle. Is this the right approach for that?

Copy link
Copy Markdown
Member

@shellmayr shellmayr left a comment

Choose a reason for hiding this comment

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

Looks good to me - it would still be a good idea in my opinion to add some tests to prevent future regressions on the project option, as well as to make sure the defaults are enforced correctly there.

Verify that the preprodSnapshotPrCommentsEnabled field persists
to the sentry:preprod_snapshot_pr_comments_enabled project option.

Refs EME-999
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@runningcode runningcode enabled auto-merge (squash) April 2, 2026 14:55
@runningcode
Copy link
Copy Markdown
Contributor Author

Thank you! I added a small test

@runningcode runningcode merged commit ad40621 into master Apr 2, 2026
107 checks passed
@runningcode runningcode deleted the no/eme-999-snapshot-pr-comments-flag branch April 2, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants