ci(frontend-deploy): announce a deploy when it starts - #8398
ci(frontend-deploy): announce a deploy when it starts#8398talissoncosta wants to merge 1 commit into
Conversation
The channel went quiet for the eleven minutes between a push and its outcome, so there was no way to tell a deploy was in flight, which is exactly when that matters: it is the window in which pushing again supersedes someone. Adds a card at the start, carrying the commit and who pushed it, like the outcome card. It has no needs, so it lands within seconds rather than after the tests. The action's conclusion input becomes state, since in_progress is not a conclusion. Distinct emoji and no Open Production button, because the two cards otherwise look alike while scanning and production has not changed yet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe Slack notification action now uses a Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This PR adds an in-progress deployment notification without changing deployment execution, and no actionable merge-blocking risk remains beyond normal checks and review. ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8398 +/- ##
========================================
Coverage 98.81% 98.81%
========================================
Files 1620 1620
Lines 65908 66157 +249
========================================
+ Hits 65124 65373 +249
Misses 784 784 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Docker builds report
|
github-actions
Bot
added
ci-cd
✅ private-cloud · depot-ubuntu-latest-16 — run #19907 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-16)
Details
🗂️ Previous results✅ private-cloud · depot-ubuntu-latest-arm-16 — run #19907 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)
Details
Skipped testsfirefox › tests/onboarding-tests.pw.ts › Onboarding › New user connects via the single-page onboarding flow @oss ✅ oss · depot-ubuntu-latest-arm-16 — run #19907 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-arm-16)
Details
✅ oss · depot-ubuntu-latest-16 — run #19907 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-16)
Details
|
Visual Regression19 screenshots compared. See report for details. |
1 participant
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
Follows #8371. That PR collapsed the deploy channel to one message per run, at the end. The side effect is eleven minutes of silence between a push and its outcome, so there is no way to tell a deploy is in flight, which is exactly when it matters: that is the window in which pushing again supersedes someone.
needs, so it lands within seconds of the push rather than after the tests.conclusioninput becomesstate, sincein_progressis not a conclusion.⏳ rather than 🚀, and no Open Production button: the two cards otherwise look alike while scanning the channel, and production is still on the previous release.
Starting
How did you test this code?
Rendered all four states through Slack's Block Kit Builder using the action's real
payload.jq:in_progresssuccesscancelledfailureThe start card passes no timings, so the Started and Duration fields drop out on their own, which the outcome card already relied on for its degraded path.
Both files parse as YAML. Not exercised end to end, since this workflow only runs on push to
main. The step iscontinue-on-error: trueand the job is independent of the deploy chain, so a Slack outage cannot hold up or fail a deploy.