feat(notifications): improve deploy email subjects#110348
Merged
Conversation
JoshFerge
reviewed
Mar 10, 2026
Member
JoshFerge
left a comment
There was a problem hiding this comment.
only thought is maybe we feature flag to our orgs for a day and make sure all looks good?
Member
Author
|
@JoshFerge low risk imo feature flag complexity is too high given how we use them. worst case we just revert it if for some reason it ends up being an awful idea (tho i doubt it) |
JoshFerge
approved these changes
Mar 10, 2026
Co-authored-by: Christinarlong <60594860+Christinarlong@users.noreply.github.com>
Contributor
Backend Test FailuresFailures on
|
Use the intended deploy email subject format for release notifications when project slugs are included. Update the release mail tests to assert the new subject text so the change is covered. Co-Authored-By: Codex <noreply@openai.com>
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Keep the no-project subject fallback aligned with the per-recipient deploy\nsubject format. This preserves the title used when no recipient context\nis available and addresses the remaining review-bot regression note.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improve deploy email subjects so they no longer use a reply-style
Re:prefix and instead include the projects visible to the recipient.These deploy emails were not actually threading against anything useful, and the old subject omitted the project context people use to scan notifications. This change builds the subject from the same recipient-filtered project list shown in the email body, sorts that list alphabetically, and caps longer lists with
+N moreto keep the subject readable.The change is intentionally limited to the deploy email path. It also adds regression coverage for recipient-scoped deploy subjects and for group-less activity emails so future subject/threading changes do not reintroduce this behavior.