Improve Slack notification

[glenn-jocher]

🤖 Generated by Copilot at b5c041c

Summary

♻️💬❎

Refactor slack notification logic in ci-testing.yml workflow. Add a new job to send one message on failure instead of multiple messages from each job.

Sing, O Muse, of the cunning refactorer
Who tamed the slack notification logic
In the ci-testing.yml workflow of code
And made it simpler and more efficient.

Walkthrough

• Consolidate slack notification logic into one job called NotifyFailure (link). This job runs after all the other jobs in the workflow and checks their status using the needs and if keywords. If any of the previous jobs failed, it sends a single message to the slack channel with the workflow name, run number, and commit SHA. This avoids duplicate notifications for the same workflow failure, which could be noisy and confusing.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Refinement of CI notifications and enhancing workflow triggers for user-initiated actions.

📊 Key Changes

• 🔄 Updated GitHub Actions workflows for more targeted failure notifications.
• 🔧 Removed direct Slack notifications on every failure.
• 📬 Replaced with a conditional notification mechanism that checks for failures in specific jobs ('Benchmarks' and 'Tests').
• 🚀 Added "workflow_dispatch" to manually trigger workflows for code analysis and Docker image publication.

🎯 Purpose & Impact

• 🎯 Aim to declutter unnecessary notifications and only alert when crucial jobs fail, increasing attention to significant issues.
• 💡 Impact is more streamlined and user-controlled CI processes, giving developers and maintainers better oversight and control over the codebase and deployment pipelines.
• 👥 Non-expert users benefit from a more stable and monitored system, as critical errors are promptly and efficiently managed.