Bump @actions/github from 5.1.1 to 6.0.0 #78
Annotations
4 warnings and 2 notices
Use of setFailed is considered harmful:
src/main.ts#L92
Imagine if setFailed was a dangerous function. This annotation
will highlight its usage in diffs.
And this body would describe why that is, what nuances or
trade-offs, the author should consider, and perhaps some options
to use instead.
This bit doesn't support markdown, sadly, but maybe someday?
https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
|
Use of setFailed is considered harmful:
src/main.ts#L95
Imagine if setFailed was a dangerous function. This annotation
will highlight its usage in diffs.
And this body would describe why that is, what nuances or
trade-offs, the author should consider, and perhaps some options
to use instead.
This bit doesn't support markdown, sadly, but maybe someday?
https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
|
Use of setFailed is considered harmful:
src/main.ts#L98
Imagine if setFailed was a dangerous function. This annotation
will highlight its usage in diffs.
And this body would describe why that is, what nuances or
trade-offs, the author should consider, and perhaps some options
to use instead.
This bit doesn't support markdown, sadly, but maybe someday?
https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
|
Use of setFailed is considered harmful:
src/reporter.ts#L83
Imagine if setFailed was a dangerous function. This annotation
will highlight its usage in diffs.
And this body would describe why that is, what nuances or
trade-offs, the author should consider, and perhaps some options
to use instead.
This bit doesn't support markdown, sadly, but maybe someday?
https://github.community/t/checks-ability-to-include-markdown-in-line-annotations/14736/3
|
Minimal configuration test:
dist/index.js#L345
Flagged in freckle/grep-action
|
Minimal configuration test:
src/grep.ts#L85
Flagged in freckle/grep-action
|