Fix target fallback expression parsing in compiled workflows#610
Fix target fallback expression parsing in compiled workflows#610
Conversation
Use single-quoted string literals inside target fallback expressions and regenerate lockfiles so GitHub Actions parser accepts the compiled JSON-embedded expressions. Made-with: Cursor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (18)
📝 WalkthroughWalkthroughThis PR updates GitHub Actions workflow configuration files across the repository, primarily affecting target PR number handling in safe-outputs handlers. The changes normalize quote styles in JSON string literals—replacing escaped double-quotes with single quotes for the "triggering" fallback value—across multiple workflow lock files and fragment files. Metadata frontmatter hashes are updated to reflect these changes. An artifact upload step for safe-output-items is introduced in one workflow file. No changes to control flow logic or public API signatures are present. Possibly related PRs
Suggested labels
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
target: "$\{\{ inputs.target-pr-number || 'triggering' }}"Test plan
./scripts/dogfood.sh.bin/gh-aw compile --action-mode release --action-tag v0.56.0./scripts/backwards-compat.sh$\{\{ inputs.target-pr-number || 'triggering' }}at the previously failing locationsThe body of this PR is automatically managed by the Trigger Update PR Body workflow.