Fix prompt extraction for current compiled lockfiles#1207
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Fix prompt extraction for current compiled lockfiles#1207github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Replace brittle awk parsing with YAML-based extraction that supports RUNNER_TEMP prompt includes and hashed GH_AW_PROMPT_*_EOF heredoc markers. Adds regression tests for current lockfile format and legacy markers. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This replaces the lockfile prompt extractor's brittle text parsing with a YAML-based parser that reads the
Create prompt with built-in contextstep directly from compiled.lock.ymlworkflow files.What changed
awkstate machine withscripts/extract_lockfile_prompts.pyusingyaml.safe_load.\$\{RUNNER_TEMP}/gh-aw/prompts/...GH_AW_PROMPT_<hash>_EOFscripts/extract-lockfile-prompts.shas the workflow entrypoint and turned it into a thin wrapper around the new Python extractor.tests/test_extract_lockfile_prompts.py, including a fixture test against the currentgh-aw-framework-best-practices.lock.ymlformat.Validation
python -m pytest tests/test_extract_lockfile_prompts.py -qpython -m pytest tests -qCloses #1206.
What is this? | From workflow: Trigger Framework Best Practices
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.