Skip to content

Fix OptionValueNamer to handle weird scenario #577

Fix OptionValueNamer to handle weird scenario

Fix OptionValueNamer to handle weird scenario #577

Triggered via push October 23, 2024 11:02
Status Success
Total duration 1m 43s
Artifacts

linters.yml

on: push
runner / rubocop
1m 33s
runner / rubocop
runner / prettier
28s
runner / prettier
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
runner / prettier
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
runner / rubocop
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/