Skip to content

chore(backend): post emanated regulations to the Soci Telegram group - #38

Merged
lorenzocorallo merged 1 commit into
mainfrom
chore/regulations-telegram
Nov 15, 2026
Merged

lorenzocorallo merged 1 commit into
mainfrom
chore/regulations-telegram

Conversation

@lorenzocorallo

Copy link
Copy Markdown
Member

Sets REGULATIONS_TELEGRAM_CHAT_ID: "-1001897010014" (the Soci group, from t.me/c/1897010014/1/...).

REGULATIONS_TELEGRAM_TOPIC_ID stays empty on purpose: the link's topic is 1, the forum's General topic, and the Telegram Bot API refuses message_thread_id=1 ("message thread not found"). With the topic unset the backend sends topicId: null and the bot posts without a thread id, which lands in General.

Merging rolls the backend once. The bot must be a member of the group with permission to send messages and documents.

Chat -1001897010014, General topic. The link points at topic 1, which is the forum's General topic:
the Bot API rejects message_thread_id=1, so the topic stays empty and the bot posts without a thread id.
@coderabbitai

coderabbitai Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Explain Change →

Caution

Review failed

The pull request is closed.

No actionable comments were generated in the recent review.

Walkthrough

The deployment configuration sets the Telegram chat ID to -1001897010014. The topic ID remains empty, and its comment notes that the General topic should not use a message_thread_id.

Changes

Telegram deployment configuration

Layer / File(s) Summary
Telegram chat and topic settings
apps/backend/deployment.yaml
The chat ID is set to -1001897010014. The topic ID remains empty, and its comment identifies the General topic and notes that it should not use a message_thread_id.

Change: Other

Merge Risk: Minimal · up to 9eef4

This is a configuration-only change that points regulation posts at the Soci group. No concrete defect was found, and the bot must still have send permissions in the group.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c447c498-4bf9-474a-b70a-0e0b24f2e6da
Commits

Reviewing files that changed from the base of the PR and between ae9a066 and 9eef450.

Files selected for processing: 1

  • apps/backend/deployment.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@lorenzocorallo
lorenzocorallo merged commit 2c15084 into main Nov 15, 2026
1 of 2 checks passed
@lorenzocorallo
lorenzocorallo deleted the chore/regulations-telegram branch November 15, 2026 15:35
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.

1 participant