Fix broadcast "Next" button to target originating repository and branch

[quickerup]

Motivation

• Avoid hard-coded template repository names in broadcast callback data so the Telegram "Next" button targets the repository and branch that produced the message and the manual trigger check can succeed.

Description

• Updated .github/workflows/bot_mrriebor.yml to build the Telegram reply_markup using printf with GITHUB_REPOSITORY and ${GITHUB_REF_NAME:-main} instead of a hard-coded quickerup/telegram-worker-bot-template target.
• Added guidance to README.md explaining that broadcast workflow buttons must point at the repository and branch that created the Telegram message and should not hard-code template repo names.

Testing

• Verified the in-workflow shell fragment with bash -n /tmp/bot_mrriebor_run.sh which succeeded.
• Validated example workflows with node scripts/validate.js workflows/example.json which passed.
• Ran git diff --check to ensure no whitespace/errors, which returned no issues.

---

Codex Task

Summary by CodeRabbit

• Bug Fixes

  • Telegram workflow buttons now dynamically reference the repository and branch that generated the message, improving navigation reliability.

• Documentation

  • Updated manual workflow instructions to clarify repository and branch requirements for Telegram buttons.
  • Added guidance to avoid hard-coded repository references in button actions.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 29783a1e-ad37-4da1-8033-0fb2320f6653

📥 Commits

Reviewing files that changed from the base of the PR and between 44c2246 and 882c72f.

📒 Files selected for processing (2)

• .github/workflows/bot_mrriebor.yml
• README.md

---

📝 Walkthrough

Walkthrough

The Telegram workflow now generates button callback data from the current repository and ref, defaulting the branch to main. The README documents that manual broadcast buttons must target the repository and branch that created the Telegram message.

Changes

Telegram button targeting

Layer / File(s)	Summary
Dynamic callback targeting .github/workflows/bot_mrriebor.yml, README.md	Telegram buttons use GITHUB_REPOSITORY and the current ref name instead of hard-coded values, with README guidance covering the required repository and branch alignment.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• quickerup/telegram-workflow-bot#13: Adds related manual broadcast workflow instructions involving repository and branch callback alignment.
• quickerup/telegram-workflow-bot#17: Contains overlapping README documentation for manually triggering the Multi-Media Broadcast workflow.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-manual-trigger-for-multi-media-broadcast

---

_{Comment @coderabbitai help to get the list of available commands.}