Skip to content

Actions: exercism/javascript-analyzer

Actions

Format code

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
format-code.yml
47 workflow runs
47 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Format code Format code #71: created by CodequiryUS
1s
1s
Bump micromatch from 4.0.4 to 4.0.8 Format code #70: Issue comment #159 (comment) created by dependabot bot
Skipped
Skipped
Bump cross-spawn from 7.0.3 to 7.0.6 Format code #69: Issue comment #163 (comment) created by dependabot bot
11s
11s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #68: Issue comment #127 (comment) created by Steffe-Dev
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #67: Issue comment #127 (comment) created by joshgoebel
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #66: Issue comment #127 (comment) created by SleeplessByte
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #65: Issue comment #127 (comment) created by Steffe-Dev
3s
3s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #64: Issue comment #127 (comment) created by SleeplessByte
3s
3s
[Resistor Duo analyzer (#127)] Add feedback to extract the constant to the top level if defined locally Format code #63: Issue comment #164 (comment) created by Steffe-Dev
3s
3s
[Resistor Duo analyzer (#127)] Add feedback to extract the constant to the top level if defined locally Format code #62: Issue comment #164 (comment) created by Cool-Katt
3s
3s
[Resistor Duo analyzer (#127)] Add feedback to extract the constant to the top level if defined locally Format code #61: Issue comment #164 (comment) created by SleeplessByte
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #60: Issue comment #127 (comment) created by SleeplessByte
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #59: Issue comment #127 (comment) created by Steffe-Dev
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #58: Issue comment #127 (comment) created by SleeplessByte
3s
3s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #57: Issue comment #127 (comment) created by Steffe-Dev
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #56: Issue comment #127 (comment) created by Steffe-Dev
3s
3s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #55: Issue comment #127 (comment) created by SleeplessByte
3s
3s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #54: Issue comment #127 (comment) created by SleeplessByte
3s
3s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #53: Issue comment #127 (comment) created by Steffe-Dev
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #52: Issue comment #127 (comment) created by SleeplessByte
1s
1s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #51: Issue comment #127 (comment) created by joshgoebel
2s
2s
Incorrect Analysis: JavaScript analyzer makes little sense when a object literal is used Format code #50: Issue comment #127 (comment) created by Steffe-Dev
2s
2s