Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix: keep step-name-alignment manifest in workspace path
Co-authored-by: pelikhan <[email protected]>
  • Loading branch information
Copilot and pelikhan authored May 22, 2026
commit 9cc84ede465ecd60699c134f1e0d63112fee6955
28 changes: 14 additions & 14 deletions .github/workflows/step-name-alignment.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

13 changes: 7 additions & 6 deletions .github/workflows/step-name-alignment.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,10 +25,11 @@ steps:
- name: Build step alignment manifest
run: |
set -euo pipefail
mkdir -p /tmp/gh-aw/agent
AGENT_INPUT_DIR="$GITHUB_WORKSPACE/.gh-aw/agent"
mkdir -p "$AGENT_INPUT_DIR"

MANIFEST_JSONL="/tmp/gh-aw/agent/step-alignment-input.jsonl"
MANIFEST_JSON="/tmp/gh-aw/agent/step-alignment-input.json"
MANIFEST_JSONL="$AGENT_INPUT_DIR/step-alignment-input.jsonl"
MANIFEST_JSON="$AGENT_INPUT_DIR/step-alignment-input.json"
: > "$MANIFEST_JSONL"

while IFS= read -r workflow_file; do
Expand Down Expand Up @@ -68,7 +69,7 @@ You are an AI agent that ensures consistency and accuracy in step names across a
## Your Mission

Maintain consistent, accurate, and descriptive step names by:
1. Reading the pre-built manifest at `/tmp/gh-aw/agent/step-alignment-input.json`
1. Reading the pre-built manifest at `.gh-aw/agent/step-alignment-input.json`
2. Analyzing step names against their intent and context
3. Comparing terminology with the project glossary
4. Identifying inconsistencies, inaccuracies, or unclear names
Expand Down Expand Up @@ -131,7 +132,7 @@ cat docs/src/content/docs/reference/glossary.md

A deterministic pre-agent step has already collected step records from all `.lock.yml` files and written them to:

`/tmp/gh-aw/agent/step-alignment-input.json`
`.gh-aw/agent/step-alignment-input.json`

Read this manifest first and use it as your primary dataset.

Expand Down Expand Up @@ -483,4 +484,4 @@ To keep token consumption predictable:

Good luck! Your work helps maintain a consistent, professional codebase with clear, accurate step names that align with project terminology.

{{#runtime-import shared/noop-reminder.md}}
{{#runtime-import shared/noop-reminder.md}}
Loading