Revert #102 — invalid workflow YAML broke developer-docs-agent on trunk - #103
Merged
Merged
Conversation
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
1 participant
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.
PR #102's migrated
developer-docs-agent.yml/skills-agent.ymlvalidated under lenientpython yamlbut GitHub Actions' parser rejects them (invalid-workflow at L142; theworkspace_contract_checks: >-folded block with an embedded${{ }}JSON ternary — a construct the working intelligence consumer never uses). This broke the workflow on trunk (runs fail at parse with no jobs;gh workflow runcan't find the workflow).Reverting to restore the parseable (plan-only) workflow immediately. The execute-and-open-PR migration will be re-done with a GitHub-Actions-validated workflow shape.
AI assistance