Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Slack notification to mention @hub-team instead of @channel #863

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

yogendrasinghx
Copy link
Member

@yogendrasinghx yogendrasinghx commented Oct 1, 2024

This PR updates the GitHub Actions workflow to change Slack notifications from @channel to @hub-team. By mentioning @hub-team, we ensure that only the relevant team members are notified when actions fail or are cancelled.

Additional Notes

  • Please ensure that the HUB_TEAM_SLACK_ID secret is correctly set in the repository settings
  • No other changes were made to the workflow beyond the Slack notification update

I have read the CLA Document and I sign the CLA

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Improved error notifications for GitHub Actions by customizing Slack alerts.

📊 Key Changes

  • Added a new secret for Slack team ID (HUB_TEAM_SLACK_ID).
  • Updated the Slack notification to mention a specific Slack subteam instead of a channel.

🎯 Purpose & Impact

  • Focused Alerts: Alerts now target a specific team, reducing noise for non-relevant members. 📣
  • Better Coordination: Enhances team response efficiency during errors by notifying the correct group directly. 🛠️

@UltralyticsAssistant UltralyticsAssistant added the enhancement New feature or request label Oct 1, 2024
@UltralyticsAssistant
Copy link
Member

👋 Hello @yogendrasinghx, thank you for submitting an ultralytics/hub 🚀 PR! This is an automated response, and an Ultralytics engineer will also assist you soon. To ensure a seamless integration of your work, please review the following checklist:

  • 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/hub 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: You've acknowledged the Contributor License Agreement. Thank you! 😊
  • Minimize Changes: Limit your changes to the minimum necessary for your update. "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 UltralyticsAssistant merged commit 2e15f7a into main Oct 1, 2024
4 checks passed
@UltralyticsAssistant UltralyticsAssistant deleted the slack-subteam-ci branch October 1, 2024 14:40
@UltralyticsAssistant
Copy link
Member

@yogendrasinghx merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants