Org commits now ring every member's bell
Reply to, quote, star, or mention @laravel's commit and every admin and member gets a notification, worded as the organization's. Only the person who did it is left out.
You are an admin of @laravel. A stranger replies to one of the organization's commits, and your inbox says replied to @laravel's commit, with the org's square avatar. Someone mentions it. Your inbox says mentioned @laravel. Click either one and you land on the organization's commit page, not on your own.
Credit mnapoli, who taught notifications whose they are. Each notification now records the organization it was for, or nothing when it is your own, so every admin and member hears about replies, quotes and stars on its commits, and about commits that mention it, minus whoever acted. Mentioned both by name and through the org, you hear once, as yourself. A rejected org commit tells all of them with the moderator's reason, and each notice makes the member its own actor, so the inbox never reveals who posted. Members also see the org's pending and rejected commits, and their images.
One gap. Post a reply or quote as @laravel and nobody hears it. Commits made as an organization still skip the notifiers that would tell the person you answered. The org can ring your bell. It cannot answer yours yet.
Part of a larger story
Key files · #1368
- app/
Queries/ ProfileRecipientsQuery.php - app/
Actions/ CreateReplyNotifications.php - app/
Actions/ CreateMentionNotifications.php - app/
Actions/ CreateStarNotification.php - app/
Actions/ UpdateCommitStatuses.php - database/
migrations/ 2026_11_01_100000_add_organization_id_to_notifications_table.php - resources/
js/ index.tsxpages/ notification/ - app/
Queries/ CommitBuilder.php