[Due for payment 2025-08-20] Ping app deployers in Slack when CPs require conflict resolution #68299
Description
Problem
App deployers often cherry-pick a PR to resolve deploy blockers. Occasionally these cherry-picks have conflicts with the target branch. In these cases a Github issue is created for the deployer to manually resolve and fix (example).
These are sometimes missed, which causes confusion and takes time to clean up. Also, we are shipping deploy blockers to production without realising.
Solution
In addition to creating the Github issue and assigning the relevant engineers, lets post in Slack to provide a more immediate notification.
To get this out asap I'm going to just tag @app_deployers. This can be improved by directly tagging the deployer, but that be done later -- we don't currently have a way of getting Slack Id from github ID
Activity
[-]Ping app deployers in Slack when CPs require conflict resolution[/-][+][Due for payment 2025-08-20] Ping app deployers in Slack when CPs require conflict resolution[/+]melvin-bot commentedon Aug 13, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 13, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.93-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-08-20. 🎊
melvin-bot commentedon Aug 20, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
melvin-bot commentedon Aug 27, 2025
@Julesssss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Julesssss commentedon Aug 27, 2025
This is merged, for now it's fine to tag all