sqlite-web 0.7.2
gitea.db
action
Create
Query
access
access_token
action
action_artifact
action_run
action_run_index
action_run_job
action_runner
action_runner_token
action_schedule
action_schedule_spec
action_task
action_task_output
action_task_step
action_tasks_version
action_variable
app_state
attachment
auth_token
badge
branch
collaboration
comment
commit_status
commit_status_index
commit_status_summary
commit_sync_log
commit_sync_status
dbfs_data
dbfs_meta
deploy_key
email_address
email_hash
external_login_user
follow
gpg_key
gpg_key_import
hook_task
issue
issue_assignees
issue_content_history
issue_dependency
issue_index
issue_label
issue_pin
issue_user
issue_watch
label
language_stat
lfs_lock
lfs_meta_object
login_source
milestone
mirror
notice
notification
oauth2_application
oauth2_authorization_code
oauth2_grant
org_user
package
package_blob
package_blob_upload
package_cleanup_rule
package_file
package_property
package_version
project
project_board
project_issue
protected_branch
protected_tag
public_key
pull_auto_merge
pull_request
push_mirror
reaction
release
renamed_branch
repo_archiver
repo_hidden_file
repo_indexer_status
repo_license
repo_redirect
repo_topic
repo_transfer
repo_unit
repository
review
review_state
secret
session
sqlite_sequence
star
stopwatch
system_setting
task
team
team_invite
team_repo
team_unit
team_user
topic
tracked_time
two_factor
upload
user
user_badge
user_blocking
user_open_id
user_redirect
user_setting
version
watch
webauthn_credential
webhook
Toggle helper tables
Structure
Content
Query
Insert
Drop
Import
Export
Delete row 31122 from action
id
31122
user_id
5
op_type
5
act_user_id
5
repo_id
117
comment_id
0
is_deleted
0
ref_name
refs/heads/main
is_private
0
content
{"Commits":[{"Sha1":"54738a32d
{"Commits":[{"Sha1":"54738a32d101f97cc5dd3a5bca7ea426dceea9c6","Message":"feat(治理): L9 的完整仓名单带进 JSON——裁决输入不该每次重新推导\n\nL9 目前是全工作区唯一在报的那条,挂在 N-11 的裁决上,而裁决要回答的正是「哪些仓各自\n补 compose `name:`」。判定本来就算出了完整名单(composeProjectCollisions 返回\nrepos / files),但建 issue 时被丢掉:消息里只写前三个加「等 N 个」,JSON 里一个都没有。\n于是每次想知道是哪八个,都得重新推导一遍。\n\n`issue()` 增一个可选 extra 参数,只用于把**判定已算出、消息里放不下**的结构化数据带进\nJSON;没有 extra 的检查一个字段都不多(用例钉住 L13 的键仍是四个)。\n\n实测:门禁现在报出的 8 个仓与我按同一口径(排除 29 个工作树、按 .git 目录归仓)独立\n重推的结果完全一致——数字员工OS、知识云、AI项目与工单、AI人事系统、设备云、巨嗨智服、\n巨嗨报价系统、嗨赞造意/image-generation。counts 未变(total 1 / L9 1)。\n\n补两条用例:L9 的发现必须携带 repos 且数量与消息声称的一致、不得重复、files 不少于仓数;\n以及 issue() 的默认形状不变。前者守的是「有冲突时名单不得丢」,不是「必须有冲突」——\nL9 清零后它自然为空。\n\n一致性门禁测试 42 → 44,治理层全量 397 过 / 6 跳 / 0 失败。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T02:46:51-07:00"}],"HeadCommit":{"Sha1":"54738a32d101f97cc5dd3a5bca7ea426dceea9c6","Message":"feat(治理): L9 的完整仓名单带进 JSON——裁决输入不该每次重新推导\n\nL9 目前是全工作区唯一在报的那条,挂在 N-11 的裁决上,而裁决要回答的正是「哪些仓各自\n补 compose `name:`」。判定本来就算出了完整名单(composeProjectCollisions 返回\nrepos / files),但建 issue 时被丢掉:消息里只写前三个加「等 N 个」,JSON 里一个都没有。\n于是每次想知道是哪八个,都得重新推导一遍。\n\n`issue()` 增一个可选 extra 参数,只用于把**判定已算出、消息里放不下**的结构化数据带进\nJSON;没有 extra 的检查一个字段都不多(用例钉住 L13 的键仍是四个)。\n\n实测:门禁现在报出的 8 个仓与我按同一口径(排除 29 个工作树、按 .git 目录归仓)独立\n重推的结果完全一致——数字员工OS、知识云、AI项目与工单、AI人事系统、设备云、巨嗨智服、\n巨嗨报价系统、嗨赞造意/image-generation。counts 未变(total 1 / L9 1)。\n\n补两条用例:L9 的发现必须携带 repos 且数量与消息声称的一致、不得重复、files 不少于仓数;\n以及 issue() 的默认形状不变。前者守的是「有冲突时名单不得丢」,不是「必须有冲突」——\nL9 清零后它自然为空。\n\n一致性门禁测试 42 → 44,治理层全量 397 过 / 6 跳 / 0 失败。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T02:46:51-07:00"},"CompareURL":"luoanwu/platform-governance/compare/72c053ccbb2b4effb1451b6b61e69faf9c313fd5...54738a32d101f97cc5dd3a5bca7ea426dceea9c6","Len":1}
...
created_unix
1789724816
Delete
Cancel