Skip to content

fix: scope Telegram pairing code blocks#135

Merged
artemgetmann merged 4 commits into
mainfrom
codex/port-telegram-pairing-code-blocks-20260325
Mar 26, 2026
Merged

fix: scope Telegram pairing code blocks#135
artemgetmann merged 4 commits into
mainfrom
codex/port-telegram-pairing-code-blocks-20260325

Conversation

@artemgetmann
Copy link
Copy Markdown
Owner

Summary

  • port upstream commit 149c4683a3 for Telegram pairing message formatting
  • keep pairing codes and approve commands wrapped as Telegram HTML code blocks in the fork
  • adapt the new DM test to this fork's direct src/pairing/pairing-challenge.ts entrypoint instead of upstream's plugin-sdk wrapper
  • carry the inherited doc-formatting fix required for pnpm check in this branch

Why

  • pairing codes are easy to mistype when Telegram collapses or mangles plain text
  • the upstream behavior is worth keeping, but this fork's pairing path differs enough that the test needed a manual port instead of a blind cherry-pick

Validation

  • pnpm test -- extensions/telegram/src/dm-access.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts src/pairing/pairing-messages.test.ts src/pairing/pairing-challenge.test.ts
  • pnpm build
  • pnpm check

Risk

  • low: behavior change is limited to Telegram pairing reply rendering and associated tests
  • medium: this PR includes the same inherited docs formatting fix already needed on the prior intake branch so repo-wide check can pass

sumukhj1219 and others added 4 commits March 25, 2026 18:19
…ukhj1219)

* Telegram: format pairing challenge for easier copy

* test: restore Telegram pairing chatId assertion

* fix: scope Telegram pairing code blocks (openclaw#52784) (thanks @sumukhj1219)

---------

Co-authored-by: Ayaan Zaidi <hi@obviy.us>
- what: apply repo formatter output to the upstream intake report and consumer execution spec already present on `main`
- why: `pnpm check` failed on inherited markdown formatting, so this keeps the Telegram port branch green without changing document meaning
- risk: docs-only formatting churn in two existing files
…airing-code-blocks-mergefix-20260326

# Conflicts:
#	CHANGELOG.md
@artemgetmann artemgetmann merged commit e575ad1 into main Mar 26, 2026
1 of 3 checks passed
@artemgetmann artemgetmann deleted the codex/port-telegram-pairing-code-blocks-20260325 branch March 26, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants