Update bot configuration with real credentials

[Panday260]

Updated API_KEY, OWNER_ID, and OWNER_USERNAME with actual values.

Summary by Sourcery

Update the sample bot configuration to use specific API credentials and owner information instead of placeholder values.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Replaces placeholder bot configuration values in the sample config with concrete API credentials and owner identity, changing only the required configuration constants in the sample config file.

File-Level Changes

Change	Details	Files
Replace placeholder configuration values with concrete credentials and owner identifiers in the sample bot config.	Set API_KEY to a concrete Telegram bot token string instead of a placeholder value. Set OWNER_ID to a specific numeric string representing the bot owner's user ID. Set OWNER_USERNAME to a specific Telegram username string for the bot owner.	tg_bot/sample_config.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Avoid committing real API keys, IDs, or usernames into the repository; keep sample_config.py as a template with placeholders and load actual credentials from environment variables or a local, ignored config file instead.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Avoid committing real API keys, IDs, or usernames into the repository; keep `sample_config.py` as a template with placeholders and load actual credentials from environment variables or a local, ignored config file instead.

## Individual Comments

### Comment 1
<location path="tg_bot/sample_config.py" line_range="13-15" />
<code_context>
-    API_KEY = "YOUR KEY HERE"
-    OWNER_ID = "YOUR ID HERE"  # If you dont know, run the bot and do /id in your private chat with it
-    OWNER_USERNAME = "YOUR USERNAME HERE"
+    API_KEY = "8688975164:AAGP8NSDkxU7wH6iLhmiCZ-hYsKN2Ehf0OU"
+    OWNER_ID = "6978422074"  # If you dont know, run the bot and do /id in your private chat with it
+    OWNER_USERNAME = "Mr_1PaNDaY"

     # RECOMMENDED
</code_context>
<issue_to_address>
**🚨 issue (security):** Avoid committing real API keys and personal identifiers in sample config; keep placeholders or use env vars instead.

Including what looks like a real bot API key, owner ID, and username here is a security and privacy issue, especially in a public/shared repo, and sets a bad example for consumers of this sample. If this key has been pushed to any remote, rotate it immediately and invalidate the old one.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

🚨 issue (security): Avoid committing real API keys and personal identifiers in sample config; keep placeholders or use env vars instead.

Including what looks like a real bot API key, owner ID, and username here is a security and privacy issue, especially in a public/shared repo, and sets a bad example for consumers of this sample. If this key has been pushed to any remote, rotate it immediately and invalidate the old one.