SQLite Web: gitea.db

id

Primary key. INTEGER NOT NULL

user_id

INTEGER

op_type

INTEGER

act_user_id

INTEGER

repo_id

INTEGER

comment_id

INTEGER

is_deleted

INTEGER NOT NULL (default 0

ref_name

TEXT

is_private

INTEGER NOT NULL (default 0

content

{"Commits":[{"Sha1":"aa3f9e8b4a7ff81e2d629a00345bab76bd22898e","Message":"ci(gitea): 改用 step-level continue-on-error（Gitea 不传播 job-level 到 run conclusion）\n\nrun #23261 现象：unit-tests / governance-audit 两个 job 已设 job-level\ncontinue-on-error，但整体 run conclusion 仍 = failure。\n\n根因：Gitea act_runner v0.2.13 与 GitHub Actions 行为不同 ——\njob-level continue-on-error 只让\"依赖该 job 的下游 job\"不被阻断，\n但 Gitea 把 run 整体 conclusion 聚合为 failure（只要有 job 结论 failure，\n即便它 continue-on-error）。GitHub 则会把 continue-on-error job 视为\nneutral 不计入 run 失败。\n\n修复：在两个真正出错的 step 上加 step-level continue-on-error\n（Gitea 可靠 honor step→job→run 这条链）：\n- \"Run unit tests\" step\n- \"校验 HIGH+CRITICAL+MEDIUM=0 与 dashboard 自检\" step\njob-level continue-on-error 保留（文档化意图 + 双保险）。\nverdict / 测试结果仍打到日志，信号不丢；完整 H+C+M=0 强制仍在\n.github/workflows + 本地 pre-commit。硬门禁 frontend-typecheck /\nlint-and-typecheck 不受影响仍强制。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-15T09:58:02-07:00"}],"HeadCommit":{"Sha1":"aa3f9e8b4a7ff81e2d629a00345bab76bd22898e","Message":"ci(gitea): 改用 step-level continue-on-error（Gitea 不传播 job-level 到 run conclusion）\n\nrun #23261 现象：unit-tests / governance-audit 两个 job 已设 job-level\ncontinue-on-error，但整体 run conclusion 仍 = failure。\n\n根因：Gitea act_runner v0.2.13 与 GitHub Actions 行为不同 ——\njob-level continue-on-error 只让\"依赖该 job 的下游 job\"不被阻断，\n但 Gitea 把 run 整体 conclusion 聚合为 failure（只要有 job 结论 failure，\n即便它 continue-on-error）。GitHub 则会把 continue-on-error job 视为\nneutral 不计入 run 失败。\n\n修复：在两个真正出错的 step 上加 step-level continue-on-error\n（Gitea 可靠 honor step→job→run 这条链）：\n- \"Run unit tests\" step\n- \"校验 HIGH+CRITICAL+MEDIUM=0 与 dashboard 自检\" step\njob-level continue-on-error 保留（文档化意图 + 双保险）。\nverdict / 测试结果仍打到日志，信号不丢；完整 H+C+M=0 强制仍在\n.github/workflows + 本地 pre-commit。硬门禁 frontend-typecheck /\nlint-and-typecheck 不受影响仍强制。\n\nCo-Authored-By: Claude Opus 4.7 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-05-15T09:58:02-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/58dfbcbadca38d7a2f0fd6fa5b7ed48281afd735...aa3f9e8b4a7ff81e2d629a00345bab76bd22898e","Len":1}

TEXT

created_unix

INTEGER

Update row 2152 in action