chore(ci): add action metadata guardrails - #8
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 062a56bfc6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| using=$(awk -F"'" '/^ using:/{print $2}' "$action_file" | head -n1) | ||
| main=$(awk -F"'" '/^ main:/{print $2}' "$action_file" | head -n1) |
There was a problem hiding this comment.
The metadata parser only extracts values wrapped in single quotes (awk -F"'"), so a valid action.yml using using: node20 or using: "node20" (same for main) is treated as missing and fails CI. This creates false negatives on formatting-only edits even when runs.using and runs.main are semantically correct, which undermines the guardrail’s stated purpose of enforcing values rather than quote style.
Useful? React with 👍 / 👎.
|
Closing as superseded by #10, which merged the action metadata validation workflow after fixing the actionlint CI failure and resolving the stale conflict path. |
1 participant
Summary
runs.using: node20andruns.main: dist/index.jsacross all action directoriesdist/index.jsexists for every actionValidation
./scripts/validate-actions.sh(pass)actionlintrun skipped because binary is not installed; CI runsrhysd/actionlint@v1Why
This reduces metadata drift and catches runtime/entrypoint mismatches early, improving compatibility and release stability.