Simplify Slack notification messages

[glenn-jocher]

Replaces the verbose multi-line Slack notifications with a single dense line — bold workflow name, status emoji, ${{ github.repository }}, and a Run backlink — matching the format used in ultralytics/portal.

• Scopes the broad <!channel> ping down to @marketing-team to cut company-wide notification noise.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🔔 This PR updates the Slack alert message in the domain-check GitHub Actions workflow to make failure notifications shorter, clearer, and directed to a specific team group.

📊 Key Changes

• Replaced the Slack notification from a broad <!channel> alert to a targeted Slack user group mention: <!subteam^S07ABRC4MLN>.
• Simplified the failure message format in .github/workflows/check_domains.yml.
• Removed extra details from the alert, such as:
  • repository URL
  • workflow author
  • event name
• Kept the most important context in the message:
  • workflow name
  • repository name
  • direct link to the failed GitHub Actions run

🎯 Purpose & Impact

• 🎯 Improves signal-to-noise ratio by notifying the right team instead of alerting an entire channel.
• ⚡ Makes failures easier to scan with a shorter, cleaner Slack message.
• 🔗 Speeds up response time by keeping a direct link to the relevant workflow run.
• 🧹 Reduces alert clutter in Slack, which can help teams focus on actionable issues faster.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 PR! This is an automated message to help with review readiness, and an engineer will assist you shortly 😊 Please review the checklist below to help ensure a smooth integration:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/docs main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

PR looks clean. The Slack payload simplification is straightforward, scoped to the changed line, and I don't see any clear bug or maintainability issue introduced by this diff.

[UltralyticsAssistant]

Merged — fantastic improvement, @glenn-jocher! 🚀

As Blaise Pascal said, “I would have written a shorter letter, but I did not have the time.” This update captures that idea perfectly: a cleaner, more focused Slack alert that reaches the right team faster and reduces noise for everyone else.

Thanks for sharpening the workflow experience with a small change that delivers clear operational value.