Skip to content

chore(notifications): Update starter platform code to use existing app #93614

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

Conversation

leeandher
Copy link
Member

We probably don't need two apps where one manages a subset of the other. This will make things a tiny bit more colocated.

@leeandher leeandher requested review from a team as code owners June 16, 2025 16:33
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 16, 2025
@leeandher leeandher requested a review from Christinarlong June 16, 2025 17:05
Copy link
Contributor

@Christinarlong Christinarlong left a comment

Choose a reason for hiding this comment

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

thx!

@leeandher leeandher merged commit 307e4e4 into master Jun 16, 2025
64 checks passed
@leeandher leeandher deleted the leander/eco-713-refactor-to-use-existing-notifications-django-app branch June 16, 2025 17:29
billyvg pushed a commit that referenced this pull request Jun 18, 2025
#93614)

We probably don't need two apps where one manages a subset of the other.
This will make things a tiny bit more colocated.
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
#93614)

We probably don't need two apps where one manages a subset of the other.
This will make things a tiny bit more colocated.
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