HI-VPN/hi-server
4
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

ci: 规范化 TG 通知与部署触发条件 #3

Closed
kxswman wants to merge 2 commits from agent/agent/ef523e06 into main
pull from: agent/agent/ef523e06
merge into: HI-VPN:main
Conversation 0 Commits 2 Files Changed 1
+142 -44
kxswman commented 2026-05-25 23:52:20 -04:00
Owner
Copy Link
Copy Source

变更摘要

  • PR 事件仅做构建验证，不执行 SCP/SSH 部署，也不发送 TG 通知
  • push 到 main / internal 才执行部署和 TG 成功/失败通知
  • TG_BOT_TOKEN / TG_CHAT_ID 已从 workflow 明文改为 Gitea Secrets 引用
  • TG 成功通知区分生产/测试环境文案
  • 修正 workflow 步骤编号

配置处理

  • 已通过 Gitea API 创建 repo Actions Secrets：TG_BOT_TOKEN、TG_CHAT_ID
  • 当前旧 Telegram Bot Token 已在 git 历史暴露，仍需要通过 BotFather 人工轮换后更新 Gitea Secret

验证

  • git diff --check origin/main...HEAD 通过
  • 本次未触发部署；合并后由 Gitea Actions 在目标分支事件中验证

回滚

如合并后需要回滚，在 main 分支执行：

git revert HEAD --no-edit && git push
## 变更摘要 - PR 事件仅做构建验证，不执行 SCP/SSH 部署，也不发送 TG 通知 - `push` 到 `main` / `internal` 才执行部署和 TG 成功/失败通知 - `TG_BOT_TOKEN` / `TG_CHAT_ID` 已从 workflow 明文改为 Gitea Secrets 引用 - TG 成功通知区分生产/测试环境文案 - 修正 workflow 步骤编号 ## 配置处理 - 已通过 Gitea API 创建 repo Actions Secrets：`TG_BOT_TOKEN`、`TG_CHAT_ID` - 当前旧 Telegram Bot Token 已在 git 历史暴露，仍需要通过 BotFather 人工轮换后更新 Gitea Secret ## 验证 - `git diff --check origin/main...HEAD` 通过 - 本次未触发部署；合并后由 Gitea Actions 在目标分支事件中验证 ## 回滚 如合并后需要回滚，在 `main` 分支执行： ```bash git revert HEAD --no-edit && git push ```
kxswman added 1 commit 2026-05-25 23:52:20 -04:00
ci: 规范化TG通知 + 安全加固 + 步骤编号修正
Build docker and publish / build (20.15.1) (pull_request) Successful in 8m20s
Details
4f82f18e16 
P01: PR 事件只做构建验证，部署步骤和TG通知仅在 push 时触发
P02: TG_BOT_TOKEN / TG_CHAT_ID 改用 secrets 引用，移除硬编码明文
P03: TG成功通知区分环境（main→生产环境 / internal→测试环境）
P04: 修正步骤编号注释（步骤1-9，消除重复的步骤5/步骤6）

注意：需在 Gitea 仓库 Settings → Secrets 中手动添加
TG_BOT_TOKEN 和 TG_CHAT_ID，并轮换已暴露的旧 Bot Token。

Co-authored-by: multica-agent <github@multica.ai>
shanshanzhong147 added 1 commit 2026-05-26 00:16:56 -04:00
ci: gate image push and add deploy health rollback
Build docker and publish / build (20.15.1) (pull_request) Successful in 8m3s
Details
ea1de71146 
Co-authored-by: multica-agent <github@multica.ai>
shanshanzhong147 closed this pull request 2026-05-26 11:08:03 -04:00
Some checks are pending
Build docker and publish / build (20.15.1) (pull_request) Successful in 8m3s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kxswman pignored9 sepakeloudest shanshanzhong147
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: HI-VPN/hi-server#3
Delete Branch "agent/agent/ef523e06"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?