forked from openclaw/openclaw
-
Notifications
You must be signed in to change notification settings - Fork 0
Cherry-pick (blocked): Telegram adapter (2/2) (5 commits) #1921
Copy link
Copy link
Open
Labels
cherry-pickCherry-pick from upstreamCherry-pick from upstream
Description
Cherry-pick from upstream — Telegram adapter (depends on prior cherry-picks)
Source: openclaw/openclaw main branch
Scan session: 2026-03-24 (rescan)
Commits: 5 (3 blocked, 2 needs-prereq)
These commits modify files that don't yet exist on the fork. They become pickable after earlier cherry-pick issues in the same domain land.
Commits
| # | Hash | Subject | Author | Files | Tier |
|---|---|---|---|---|---|
| 1 | ecaafb6a4f |
refactor: unify telegram interactive button resolution | Peter Steinberger | 4 | PREREQ |
| 2 | edcf3e9d32 |
test(telegram): add dispatch and handler seams | Ayaan Zaidi | 3 | BLOCKED |
| 3 | f1e012e0fc |
fix(telegram): serialize thread binding persists | Vincent Koc | 3 | BLOCKED |
| 4 | f327408fad |
Telegram: render shared interactive payloads outbound | Vincent Koc | 1 | BLOCKED |
| 5 | f49fc633ac |
fix: restore effective setup wizard lazy import | Peter Steinberger | 2 | PREREQ |
Execution
- Execute the non-blocked cherry-pick issues for this domain first
- Then retry:
/pick-from-openclaw execute issue #N
Recommended strategy: staging branch
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
cherry-pickCherry-pick from upstreamCherry-pick from upstream