Expose GitHub-compatible expression contexts at every workflow phase - #144
Conversation
|
/kelos claude-api-review |
|
🤖 Kelos Task Status Task |
|
🤖 Open Actions Claude API Reviewer Agent @gjkim42 API Design ReviewVerdict: APPROVE The blocking finding from the previous review is resolved, and I verified each fix in the code rather than from the description. No P0/P1 issues remain; the leftover items below are optional and were already reasonably triaged. FindingsCompatibility — prior blocking finding resolved
Naming and documentation — resolved
GitHub Actions compatibility — resolved
API surface (unchanged since prior round)
Suggestions (optional)
/kelos needs-input |
|
Addressed the current Claude API review findings in
Triaged without code changes:
Validation: |
|
/kelos claude-api-review |
|
/kelos claude-review |
|
🤖 Kelos Task Status Task |
|
🤖 Open Actions Claude Reviewer Agent @gjkim42 Review SummaryVerdict: APPROVE Findings Overview
FindingsGitHub Actions compatibility
Key takeaways
|
Define one phase-aware availability contract for workflow validation, planning, and runner evaluation. Populate documented GitHub, job, strategy, action, steps, needs, and environment context values, including rerun triggering actors and current job status in action metadata expressions. Defer needs-dependent job planning safely across controller retries and preserve stored planning wire compatibility.
724995d to
f612d69
Compare
|
Addressed the latest P2 finding in the squashed commit
The API review and all remaining general-review findings are approved or optional. The PR branch now contains exactly one commit. Validation: |
What type of PR is this?
/kind api
What this PR does / why we need it:
envcontext to workflow-defined values, and preserves exact numeric values in event payloadsgithub.triggering_actoris accurateWhich issue(s) this PR is related to:
Fixes #110
Special notes for your reviewer:
The expression availability table is covered by conformance tests to keep validation and runtime context construction aligned.
Validation completed:
make updatemake testmake verifymake buildDoes this PR introduce a user-facing change?