Files
multica/server/migrations/260_issue_origin_dingtalk_chat_validate.up.sql
YYClaw c3577cb04b feat(dingtalk): add DingTalk bot integration (MUL-3958) (#4829)
Adds a DingTalk (钉钉) bot integration on the bring-your-own-app model: a
workspace admin creates their own Stream-mode robot and pastes its AppKey /
AppSecret, so no public webhook or OAuth redirect is required. Each agent gets
its own bot identity, so several agents can be distinct, separately
@-mentionable contacts in one DingTalk organization.

Supports DMs, @-mentions in groups, inbound images, /issue quick-create, and
/new. Built on the shared channel engine (ForceFresh/BareFresh, MediaResolver /
MediaRef and the intent ledger) rather than a private implementation.

Off unless MULTICA_DINGTALK_SECRET_KEY is set. Docs in en/zh/ja/ko.

Closes #4791.

Community-maintained: @yyclaw is the code owner for
server/internal/integrations/dingtalk/.
2026-08-06 15:36:02 +08:00

10 lines
521 B
SQL

-- Validate the widened issue_origin_type_check that migration 259 added
-- NOT VALID. This takes SHARE UPDATE EXCLUSIVE while scanning issue, which
-- permits normal SELECT/INSERT/UPDATE/DELETE traffic to continue — the whole
-- point of splitting the two steps across migration files (the 197/198
-- pattern).
--
-- 259 only WIDENED the allowed set, so every pre-existing row already
-- satisfies the constraint and this scan cannot fail on legacy data.
ALTER TABLE issue VALIDATE CONSTRAINT issue_origin_type_check;