Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[aw] agentic workflows out of sync

Open Beginner friendly
#63,253 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, go

Research direction

Start with the workflow sources under .github/workflows/*.md and run the repository wrapper, make recompile, to regenerate their .lock.yml files. Review the generated diff, especially agentic-token-optimizer.lock.yml, daily-harness-experiment-proposer.lock.yml, and smoke-ci.lock.yml; done means the lock files match the markdown sources and validation succeeds.

Written by the indexing model from the issue text.

Description

agentic-workflows maintenance

Problem

The workflow lock files (.lock.yml) are out of sync with their source markdown files (.md). This means the workflows that run in GitHub Actions are not using the latest configuration.

What needs to be done

The workflows need to be recompiled to regenerate the lock files from the markdown sources.

Instructions

If the repository provides a wrapper such as make recompile, prefer that command so compilation uses the repository's canonical flags. In github/gh-aw, any edit under .github/workflows/*.md should be followed by make recompile before committing.

Recompile all workflows using one of the following methods:

Using the repository wrapper
make recompile
Using gh aw CLI
gh aw compile --validate --verbose
Using gh-aw MCP Server

If you have the gh-aw MCP server configured, use the compile tool:

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

This will:

  1. Build the latest version of gh-aw
  2. Compile all workflow markdown files to YAML lock files
  3. Ensure all workflows are up to date

After recompiling, commit the changes with a message like:

Recompile workflows to update lock files

Detected Changes

The following workflow lock files have changes:

View diff
diff --git a/.github/workflows/agentic-token-optimizer.lock.yml b/.github/workflows/agentic-token-optimizer.lock.yml
index 250849b..42bde54 100644
--- a/.github/workflows/agentic-token-optimizer.lock.yml
+++ b/.github/workflows/agentic-token-optimizer.lock.yml
@@ -1879,7 +1879,7 @@ jobs:
       - agent
       - evals
       - safe_outputs
-    if: always() && (!cancelled()) && needs.agent.result != 'skipped'
+    if: always() && (!cancelled())
     runs-on: ubuntu-slim
     permissions:
       contents: write
diff --git a/.github/workflows/daily-harness-experiment-proposer.lock.yml b/.github/workflows/daily-harness-experiment-proposer.lock.yml
index 03f717d..57dde49 100644
--- a/.github/workflows/daily-harness-experiment-proposer.lock.yml
+++ b/.github/workflows/daily-harness-experiment-proposer.lock.yml
@@ -1995,7 +1995,7 @@ jobs:
       - agent
       - evals
       - safe_outputs
-    if: always() && (!cancelled()) && needs.agent.result != 'skipped'
+    if: always() && (!cancelled())
     runs-on: ubuntu-slim
     permissions:
       contents: write
diff --git a/.github/workflows/smoke-ci.lock.yml b/.github/workflows/smoke-ci.lock.yml
index a7fb2ca..7421697 100644
--- a/.github/workflows/smoke-ci.lock.yml
+++ b/.github/workflows/smoke-ci.lock.yml
@@ -1800,7 +1800,7 @@ jobs:
       - activation
       - agent
       - safe_outputs
-    if: always() && (!cancelled()) && needs.agent.result != 'skipped'
+    if: always() && (!cancelled())
     runs-on: ubuntu-slim
     permissions:
       contents: write

References

  • Repository: github/gh-aw

Generated by Agentic Maintenance

Dominant language
Go
Stars
5.2k
Forks
547
Avg merge
6h 23m
Merged PRs (30d)
760

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw

All issues in github/gh-aw

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.