- Allows verbose reporting of Issues in Run Terminal/Log.
- Correctly maps Issue Severity to GitHub Severity
- Additionally adds support for Severity Failure levels (defaults to 'notice' [all])
- Adds suggested fixes to Annotation Raw Details
- Prepares foundation for supporting Comments
- Adds support for Multi-Line Annotations
- Adds mapping for common Issue Severities to GitHub Severities (Code climate | Checkstyle | GitHub)
- Adds handeling of 'Ignore' Issue Severity (removes from Issue List)
- Adds support for Character Range Annotations

This was surprisingly difficult.  This is pretty reliable, using low-cost methods (filtering on Name comparison, Annotation count [we add one, so it should have atleast one]) and then searching for a unique string if the count is still higher than 1.

I'm pretty happy about this, I think this will stand the test of time until GitHub get's their act together...

…se pause.

Add a Setup (Pre-Main) action to prepare the Env and begin CheckRun Resolution.

With any luck, this will solve that little issue, otherwise I give up.

I have been jumping through way too many hoops to make the non-standard checks on origin behave properly, oh well.

It is indicating it is not getting Check Suite Information, which is unlikely.