sv-oss/ESBuild Metafile Analysis

Generates a PR comment based on the metafile data analysis completed

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
github-tokenThe Github token to useyes${{ github.token }}
generate-metafiles-commandThe command to execute within the repo to generate the metafiles in the directoryyesnpm run synth
metafile-directoryThe directory in the file-system where to source all metafilesyes
metafile-globA glob to filter out and include only specific metafilesno**/*.json
comment-headerAny details to put in the header of the comment before rendering the table of files
comment-footerAny details to put at the end of the comment after rendering the table of files
comment-threshold-criticalThe file size (including unit) to start marking files as a critical status5mb
comment-threshold-highThe file size (including unit) to start marking files as a high status1mb
comment-threshold-mediumThe file size (including unit) to start marking files as a medium status500kb
comment-threshold-lowThe file size (including unit) to start marking files as a low status300kb
comment-large-node-modules-thresholdThe threshold to start adding the specific node_modules in the list of large node_modules25kb
comment-min-thresholdThe minimum severity to render in the comment. By default, all files will be rendered. Accepted values are CRITICAL/HIGH/MEDIUM/LOW/INFOLOW
check-mark-failureWhether to add a check to the Pull Request as a failure when any file meets the threshold limittrue
check-mark-file-countThe number of files that need to reach the threshold to mark the Pull Request as a failure1
check-mark-min-thresholdThe threshold for considering a file as a failure for whether or not to add a checkHIGH
display-summaryWhether to render the summary of filestrue
display-key-issuesWhether to render the key issues that were foundtrue
display-deltasWhether to render the file deltas that were detectedtrue

no outputs