[aw] SelfCare / Docs Build Time: has stale lock file

已关闭 适合新手
  • 哪里不对？
#20,153 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1-3 小时
新手友好度
80/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, yaml
领域
ci-cd

调研方向

从 .github/workflows/self-care-docs-build-time-investigator.md 开始；如果原因不明显，查看失败运行中的“Check workflow lock file”步骤。运行 gh aw compile 并提交重新生成的 .lock.yml 文件。当编译后的锁文件与工作流源文件一致时即完成。

由索引模型根据 Issue 内容生成。

描述

agentic-workflows
What happened

SelfCare / Docs Build Time has stale lock file.

View run #41638821449 · Workflow source · Previous failures

Branch: main

Next step

Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.

Failure details

[!WARNING]
Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

To fix, recompile the workflow:

gh aw compile

Then commit and push the updated .lock.yml file.

More ways to recompile

Using the gh-aw MCP server (if configured):

{
  "tool": "compile",
  "arguments": {
    "validate": true
  }
}

Recompile all workflows at once:

gh aw compile --all

Verify the result:

gh aw compile --validate
How to investigate the mismatch

The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

  • The raw frontmatter text that was used as input
  • Any imported files that were included in the hash
  • The canonical JSON that was fed to SHA-256
  • The resulting hash value

This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

gh aw add <path>@<exact-sha>
gh aw compile
How to disable this check

[!CAUTION]
Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

Set stale-check: false in the on: section of your workflow frontmatter:

on:
  issues:
    types: [opened]
  stale-check: false

After editing, recompile the workflow: gh aw compile

Copy a debugging prompt

Paste this into your coding agent:

Debug the agentic workflow "self-care-docs-build-time-investigator" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/githubnext/gh-cao/actions/runs/41638821449

If the repository includes the agentic-workflows skill, load it before investigating.

Manage failure notifications

To stop creating failure issues for this workflow, set this in its frontmatter and recompile:

safe-outputs:
  report-failure-as-issue: false

This only disables issue reporting; it does not fix the failure.

Generated from SelfCare / Docs Build Time · ◷

  • expires on Nov 4, 2026, 12:49 PM UTC
主要语言
JavaScript
星标
14
派生
5
平均合并
4 小时 16 分钟
30 天内合并 PR
688

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/gh-cao 的其他 Issue

查看 githubnext/gh-cao 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。