Skip to content

Explicitly specify npm project path in task calls #599

Explicitly specify npm project path in task calls

Explicitly specify npm project path in task calls #599

Triggered via pull request September 7, 2025 01:08
Status Success
Total duration 45s
Artifacts

check-yaml-task.yml

on: pull_request
run-determination
4s
run-determination
Matrix: check
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Generate problem matcher output: ./Taskfile.yml#L187
187:121 [line-length] line too long (137 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L174
174:121 [line-length] line too long (127 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L162
162:121 [line-length] line too long (127 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L148
148:121 [line-length] line too long (141 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L133
133:121 [line-length] line too long (140 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L125
125:121 [line-length] line too long (134 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L105
105:121 [line-length] line too long (134 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L70
70:121 [line-length] line too long (131 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L54
54:121 [line-length] line too long (131 > 120 characters)
Generate problem matcher output: ./Taskfile.yml#L21
21:121 [line-length] line too long (126 > 120 characters)