Skip to content

Actions: yamingmou/session-fork-core

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
12 workflow runs
12 workflow runs

Filter by Workflow

⌥ + click/return to exclude

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
v2.4.20: 打包产物不再夹带构建机残留；打包脚本在中文 Windows 上不再报解码错 CI #12: Commit aae71d2 pushed by yamingmou
28s main
main
28s
v2.4.19: 备份不再落错地方——修复分支与直接调用库都遵守你的备份设置；版本号自报与命令行一致 CI #11: Commit f1cc416 pushed by yamingmou
39s main
main
39s
v2.4.18: 说明文档现在只讲「你去的那条入口」——不再自相矛盾，也不再夹带内部术语 CI #10: Commit 2e04009 pushed by yamingmou
22s main
main
22s
v2.4.17: 措辞与命名整理（无功能变更）——注释只陈述技术依据，测试脚本改用通用命名 CI #9: Commit fb33911 pushed by yamingmou
18s main
main
18s
v2.4.16: 措辞与命名整理（无功能变更）——注释只陈述技术依据，测试脚本改用通用命名 CI #8: Commit 83e867f pushed by yamingmou
23s main
main
23s
v2.4.16: 对外面（含代码注释）不再泄漏内部口径——18 处清除，并把这条检查的口径固化成脚本 CI #7: Commit 4a3f879 pushed by yamingmou
23s main
main
23s
v2.4.15: 体检把「要修的问题」和「看一眼就行的疑点」分开——不再每打一条分支就常驻一条红 CI #6: Commit 88409de pushed by yamingmou
30s main
main
30s
v2.4.14: Windows 从「跑第一条命令就崩」变成正常可用（并上线含真 Windows 的三平台 CI） CI #5: Commit a84134f pushed by yamingmou
22s main
main
22s
修构建脚本的两处：源头漏修 + Windows 上必崩 CI #4: Commit 5175aef pushed by yamingmou
23s main
main
23s
CI 第二轮：修 Python 3.9 构建崩溃 + 测试文件编码（Windows 上写不出测试数据） CI #3: Commit 7bc997f pushed by yamingmou
52s main
main
52s
CI 首次运行就抓到 3 个真问题，一并修掉（其中 2 个本机不可能发现） CI #2: Commit c47794e pushed by yamingmou
22s main
main
22s
Windows 兼容性：中文 Windows 下不再因 emoji 编码崩掉命令（待你在 Windows 验证，未发版） CI #1: Commit db40e3e pushed by yamingmou
22s main
main
22s