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

fix: Unify batch exports setting around one common setting #25219

Merged
merged 15 commits into from
Oct 3, 2024

Conversation

benjackwhite
Copy link
Contributor

Problem

We have a separate notification setting for batch exports but no way to use it. In practice we decided that having one setting for all is just as useful so this swaps it over to use the same field.

Changes

  • The UI doesn't change as it already indicates the setting is for all pipeline destinations

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Does this work well for both Cloud and self-hosted?

How did you test this code?

@benjackwhite benjackwhite requested a review from a team September 26, 2024 06:30
Copy link
Member

@EDsCODE EDsCODE left a comment

Choose a reason for hiding this comment

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

I think this needs to be updated to respect the single field

Base automatically changed from fix/notify-on-hog-function-failures to master September 30, 2024 07:57
# Conflicts:
#	posthog/tasks/email.py
#	posthog/tasks/test/test_hog_function.py
@benjackwhite benjackwhite enabled auto-merge (squash) October 3, 2024 12:50
@benjackwhite benjackwhite merged commit fa152e8 into master Oct 3, 2024
86 checks passed
@benjackwhite benjackwhite deleted the fix/batch-exports-setting branch October 3, 2024 13:15
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.

2 participants