Skip to content

ops: bot identity check without binance-runtime environment #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pigbibi merged 1 commit into from
Oct 10, 2026
Merged

ops: bot identity check without binance-runtime environment #365

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/notify-bot-identity.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
name: Notify Bot Identity (read-only)

# Resolves the Telegram token the Binance runtime would use (main.yml deploy job:
# environment binance-runtime, secrets.TG_TOKEN) to its public bot id/username via
# secrets.TG_TOKEN, a repo-level secret; binance-runtime only holds other secrets
# and is restricted to runtime-production, so this job does not bind it) to its public bot id/username via
# getMe, and compares it with the unified QSL资产管家 bot (8334367951).
# Prints only bot id / username; never prints token or chat id; sends no message;
# does not re-enable main.yml or change any secret.
Expand All @@ -16,7 +17,6 @@ jobs:
name: TG_TOKEN bot identity (read-only)
runs-on: ubuntu-latest
timeout-minutes: 5
environment: binance-runtime
env:
TG_TOKEN: ${{ secrets.TG_TOKEN }}
TELEGRAM_TOKEN: ${{ secrets.TELEGRAM_TOKEN }}
Expand Down
Loading