chore: use org-level TG_TOKEN secret#306
Conversation
STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN secret → org-level TG_TOKEN Co-Authored-By: Claude <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d7c17bd77b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| STRATEGY_PLUGIN_ALERT_PUSH_APP_TOKEN: ${{ secrets.STRATEGY_PLUGIN_ALERT_PUSH_APP_TOKEN }} | ||
| STRATEGY_PLUGIN_ALERT_PUSH_ACCESS_TOKEN: ${{ secrets.STRATEGY_PLUGIN_ALERT_PUSH_ACCESS_TOKEN }} | ||
| STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN: ${{ secrets.STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN }} | ||
| STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN: ${{ secrets.TG_TOKEN }} |
There was a problem hiding this comment.
When bash tests/test_sync_cloud_run_env_workflow.sh is run, it now exits 1 because the script still greps for STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN: ${{ secrets.STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN }} while this workflow now emits secrets.TG_TOKEN. Please update the workflow test alongside this secret rename so the repo’s validation for this deployment workflow remains usable.
Useful? React with 👍 / 👎.
改动
STRATEGY_PLUGIN_ALERT_TELEGRAM_BOT_TOKEN改为从 org-levelTG_TOKENsecret 读取。环境变量名不变，Cloud Run 运行时不受影响。
前置条件
TG_TOKEN已创建（需 org admin）🤖 Generated with Claude Code