(MOT-4299) refactor: delegate release notifications to Release Control - #727
(MOT-4299) refactor: delegate release notifications to Release Control#727ytallo wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
skill-check — worker0 verified, 54 skipped (no docs/).
Four for four. Nicely done. |
What changed
--notification-resultCLI argument as an ignored compatibility input for reruns of older workflowsWhy
Release and promotion are two states of the same deployment. Posting from independent workflows created duplicate root messages and coupled notification mechanics to execution evidence.
Impact
GitHub Actions now executes releases and emits terminal evidence only. The companion Release Control change consumes correlated evidence, maintains one root message per Release run, and keeps history in its thread. Out-of-band runs that are not correlated to a Release Control operation no longer notify Slack.
Companion: iii-hq/release-control#4
Validation
release_result.pytestsgit diff --checkRefs MOT-4299