fix(push): render created tags/branches as create events instead of 0 commits

docs/guide/faq.md

@@ -20,6 +20,10 @@ Check in order:
 - The user must run `/gh login` first and the OAuth secrets (`GITHUB_CLIENT_ID` / `GITHUB_CLIENT_SECRET`, `BASE_URL`) must be configured.
 - Slash commands sync from the scheduled trigger every 5 minutes; global registration can take ~1 hour to propagate.
 
+## I created a tag/branch but got a "0 commits" push message
+
+Creating a tag or an empty branch via `git push` arrives as a push event with `created: true` and no commits — since the event carries the `created` flag, it is rendered as a normal `create` message. If you still see "0 commits", the payload's `created` flag was absent (e.g. an old or non-conforming delivery).
+
 ## I deleted a branch but got a "0 commits" push message
 
 Branch deletions via `git push --delete` arrive as push events with `deleted: true` — they are rendered as a normal delete message. If you still see "0 commits", the payload's `deleted` flag was absent (e.g. an old delivery).

docs/zh/guide/faq.md

@@ -20,6 +20,10 @@
 - 用户需先执行 `/gh login`，且 OAuth 密钥（`GITHUB_CLIENT_ID` / `GITHUB_CLIENT_SECRET`、`BASE_URL`）已配置。
 - 斜杠命令由定时任务每 5 分钟同步；全局注册可能需要约 1 小时传播。
 
+## 创建标签/分支后收到"0 个提交"的推送消息
+
+通过 `git push` 创建标签或空分支时，事件以 `created: true` 且无提交的 push 事件到达——由于载荷带有 `created` 标志，会被渲染为正常的创建消息。若仍看到"0 个提交"，说明载荷中缺少 `created` 标志（例如旧或不合规的投递）。
+
 ## 删除分支后收到"0 个提交"的推送消息
 
 通过 `git push --delete` 删除分支时，事件以 `deleted: true` 的 push 事件到达——会被渲染为正常的删除消息。若仍看到"0 个提交"，说明载荷中缺少 `deleted` 标志（例如旧投递）。