openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@6308d2a1dc

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-30 05:03:41 +00:00
parent 7bc60d1115
commit f79b7e5ada
2 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "8dc99feb5097126b7f0501115b6aa2e4032c9efe",
"syncedAt": "2026-04-30T04:48:26.004Z"
"sha": "6308d2a1dcd4583bf64fa64b995c84e9348f3af1",
"syncedAt": "2026-04-30T05:01:59.886Z"
}

9
docs/ci.md
View File

@ -299,12 +299,13 @@ The `CodeQL Critical Quality` workflow is the matching non-security shard. It
runs only error-severity, non-security JavaScript/TypeScript quality queries
over narrow high-value surfaces on the smaller Blacksmith Linux runner. Its
pull request guard is intentionally smaller than the scheduled profile: non-draft
PRs only run the matching `gateway-runtime-boundary`, `provider-runtime-boundary`,
`plugin-boundary`, and `plugin-sdk-package-contract` shards for gateway
PRs only run the matching `channel-runtime-boundary`,
`gateway-runtime-boundary`, `provider-runtime-boundary`, `plugin-boundary`, and
`plugin-sdk-package-contract` shards for channel runtime, gateway
protocol/server-method, provider runtime/model catalog, plugin loader, Plugin
SDK, or package-contract changes. CodeQL config and quality workflow changes run
all four PR quality shards. Its manual dispatch accepts
`profile=all|gateway-runtime-boundary|plugin-boundary|plugin-sdk-package-contract|plugin-sdk-reply-runtime|provider-runtime-boundary|session-diagnostics-boundary`;
all five PR quality shards. Its manual dispatch accepts
`profile=all|channel-runtime-boundary|gateway-runtime-boundary|plugin-boundary|plugin-sdk-package-contract|plugin-sdk-reply-runtime|provider-runtime-boundary|session-diagnostics-boundary`;
the narrow profiles are teaching/iteration hooks for running one quality shard
in isolation without dispatching the rest of the workflow.
Its