chore(ci): force re-trigger common-plat workflow
Empty commit '1035b730' and the earlier eslint.config fix '9be49acb' did not trigger new CI runs on this Gitea instance — suspect Gitea's push-event coalescing during the runner backlog caused by parallel fastgap jobs. Adding a one-line comment to eslint.config.js to force a content-different push and a fresh run.
This commit is contained in:
parent
1035b73042
commit
7ae6085235
@ -12,6 +12,8 @@ export default [
|
|||||||
'*.config.ts',
|
'*.config.ts',
|
||||||
'**/dist/**',
|
'**/dist/**',
|
||||||
'__LOCAL_LLMs/**',
|
'__LOCAL_LLMs/**',
|
||||||
|
// (re-trigger CI: 2026-05-23)
|
||||||
|
|
||||||
// Python virtual env in extraction-service/python ships with
|
// Python virtual env in extraction-service/python ships with
|
||||||
// urllib3's emscripten worker stubs (JS files that reference
|
// urllib3's emscripten worker stubs (JS files that reference
|
||||||
// browser globals like `self`, `fetch`, `TextEncoder`). Those
|
// browser globals like `self`, `fetch`, `TextEncoder`). Those
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user