Skip to content

Latest commit

 

History

History
25 lines (17 loc) · 1.23 KB

File metadata and controls

25 lines (17 loc) · 1.23 KB

Repository Instructions

Project Shape

Build And Validation

  • Use npm run build to regenerate dist/index.js; keep the generated file in the same change when source or action metadata changes.
  • Use npm run typecheck, npm run test, and npm run fmtcheck for code changes before pushing.
  • For docs-only changes, no npm validation is required unless the docs describe action inputs, outputs, or runtime behavior that should be checked against code.

Bundling

  • Keep bundling on esbuild through the existing npm run build script.
  • Do not reintroduce @vercel/ncc for routine builds; the current dependency set relies on package exports that ncc has previously failed to bundle correctly.
  • Keep the esbuild target aligned with the action runtime in action.yml.

Docs

  • Keep README inputs and outputs aligned with action.yml and the source input parsing.
  • Add changelog entries for user-facing behavior that has merged to master but has not been released yet.
  • Use repository-relative links in tracked docs.