feat: add project names to Slack deployment titles - #10928
Open
dunctk wants to merge 3 commits into
Open
Conversation
dunctk
marked this pull request as ready for review
July 14, 2026 13:35
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.
Changes
/notifications/slackto prefix deployment notification titles with the project name.Issues
Category
Preview
The Deployments section now includes a
Show Project Name in Titlecheckbox. It was verified checked and persisted after a hard reload while global Slack delivery remained disabled and the webhook remained blank.AI Assistance
If AI was used:
Testing
/api/healthreturnedOK.php artisan test --compact tests/Feature/SlackNotificationProjectNameTest.php(2 tests, 5 assertions).vendor/bin/pint --format agenton all changed PHP files andvendor/bin/pint --dirty --format agent./notifications/slackin a real browser: the option saved, remained checked after reload, and produced no browser console errors.Contributor Agreement
Important