There is no explanation why or in which cases it could be useful. I got it working without it.
Potential explanation???
I'm guessing that if for some weird reason you'd like to run linting code and ataylorme/eslint-annotate-action in different jobs, then you could use actions/upload-artifact to save the report json file, so it could be loaded by next job that uses ataylorme/eslint-annotate-action, but currently i don't understand why would someone do that either.
Suggestion
Just remove the step related to actions/upload-artifact action from the usage example or add comment why that could be useful
Currently usage example contains:
There is no explanation why or in which cases it could be useful. I got it working without it.
Potential explanation???
I'm guessing that if for some weird reason you'd like to run linting code and
ataylorme/eslint-annotate-action
in different jobs, then you could useactions/upload-artifact
to save the report json file, so it could be loaded by next job that usesataylorme/eslint-annotate-action
, but currently i don't understand why would someone do that either.Suggestion
Just remove the step related to
actions/upload-artifact
action from the usage example or add comment why that could be useful