-
Notifications
You must be signed in to change notification settings - Fork 467
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
Find a better way to clearly notify broken master #27490
Comments
Main reporting yaml here .github/workflows/build-report.yml making vars.SLACK_REPORT_CHANNEL conditional |
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 3, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 3, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 3, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 3, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 9, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 9, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 9, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 11, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 11, 2024
victoralfaro-dotcms
added a commit
that referenced
this issue
Apr 11, 2024
Let's pass it for now and will send back if this is not working as expected. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
No response
Task
Currently if master fails to build (e.g. failing tests) there's no clear visibility for the interested parties.
We need to find an effective way to communicate when this happens.
master-build-status
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
Acceptance Criteria
Upon master failing to build, have a clear and explicit message sent to the Slack channel
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: