fix: Redirect address after successful tg binding

[tbphp]

tg绑定成功之后调整地址修改为现在的个人中心地址 /console/personal。
目前代码中还是老版本的 /setting ，已经不存在。

Summary by CodeRabbit

• New Features
  • After successfully binding a Telegram account, users are now redirected to the Personal Console (/console/personal) instead of the Settings page. This change provides a clearer landing context immediately after linking, making it easier to review personal information and related options without additional navigation. No other user-facing behavior, error handling, or flow has been modified as part of this update.

[coderabbitai]

Walkthrough

Updated Telegram binding redirect: after a successful bind, the handler now redirects from /setting to /console/personal. No other logic or error handling was changed.

Changes

Cohort / File(s)	Summary
Telegram bind redirect controller/telegram.go	Redirect target after successful TelegramBind changed from /setting to /console/personal.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant Web as Web Server
  participant Ctrl as Telegram Controller

  User->>Web: Complete Telegram bind
  Web->>Ctrl: TelegramBind()
  Ctrl-->>Web: Success status
  Note over Ctrl,Web: On success, redirect target updated
  Web-->>User: HTTP 302 → /console/personal
  alt Bind error
    Web-->>User: Error response (unchanged)
  end

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hop through routes with carrot zeal,
From /setting’s fields to console’s wheel—
A gentle nudge, a tidy trail,
Redirect set, we shall not fail.
Thump-thump! New path, same happy feel. 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly describes the primary change by indicating a fix to the redirect address following a successful Telegram binding, which aligns directly with the modifications made in the pull request.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9f989fc and d249532.

📒 Files selected for processing (1)

• controller/telegram.go (1 hunks)

🔇 Additional comments (1)

controller/telegram.go (1)

68-68: Redirect target updated appropriately.

The redirect now points to the active personal center route, matching the current console structure. ✅

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[tbphp]

测试通过，重定向正常。