Since #1796, channel packages declare their settings and the instance Channels page builds their form from extension-settings. Telegram is the exception: its bot token and allowed users are still channel-settings fields (used by setup, reload and reconcile) that the messaging service merges into the extension's settings at start, and the page renders them from that resource instead of the declared schema.
Done when Telegram's connection is stored in extension-settings like every other channel, channel-settings keeps only session defaults, and the page has no Telegram special case.
Since #1796, channel packages declare their settings and the instance Channels page builds their form from extension-settings. Telegram is the exception: its bot token and allowed users are still channel-settings fields (used by setup, reload and reconcile) that the messaging service merges into the extension's settings at start, and the page renders them from that resource instead of the declared schema.
Done when Telegram's connection is stored in extension-settings like every other channel, channel-settings keeps only session defaults, and the page has no Telegram special case.
Done in af757762. Telegram token_ref and allowed_user_ids now live in extension-settings (telegram package); channel-settings keeps session defaults plus allowed_user_ids/agent for org bots. State Store start migrates stored values once; [chat.telegram] seeds extension-settings on a fresh store. The Channels page renders Telegram through ExtensionChannelSettings. task check passes.
Done in af757762. Telegram token_ref and allowed_user_ids now live in extension-settings (telegram package); channel-settings keeps session defaults plus allowed_user_ids/agent for org bots. State Store start migrates stored values once; [chat.telegram] seeds extension-settings on a fresh store. The Channels page renders Telegram through ExtensionChannelSettings. task check passes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Since #1796, channel packages declare their settings and the instance Channels page builds their form from extension-settings. Telegram is the exception: its bot token and allowed users are still channel-settings fields (used by setup, reload and reconcile) that the messaging service merges into the extension's settings at start, and the page renders them from that resource instead of the declared schema.
Done when Telegram's connection is stored in extension-settings like every other channel, channel-settings keeps only session defaults, and the page has no Telegram special case.
Done in
af757762. Telegram token_ref and allowed_user_ids now live in extension-settings (telegram package); channel-settings keeps session defaults plus allowed_user_ids/agent for org bots. State Store start migrates stored values once; [chat.telegram] seeds extension-settings on a fresh store. The Channels page renders Telegram through ExtensionChannelSettings. task check passes.