James Brundage

HelpOut would work well in Docker. * [ ] #182 * [ ] #183 * [ ] #191 * [ ] #193 * [ ] #194

If you get help on a command with bad parameter metadata, it will error, thus causing Get-MarkdownHelp to error. It somewhat helpfully informs you what parameter was broken, but it...

Conventions from [PipeScript](https://github.com/StartAutomating/PipeScript): * [ ] HelpOut Build files should be consolidated beneath `/Build` * [ ] HelpOut Commands should be consolidated beneath `/Commands` Conventions from [EZOut](https://github.com/StartAutomating/EZOut): * [ ]...

As HelpOut runs, several events should be generated. These events can be used for tracing (see #171, #173) * [ ] Event `Get-MarkdownHelp.Input` should track input to `Get-MarkdownHelp` * [...

[Github Job Summaries](https://docs.github.com/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary) are useful ways to track output. HelpOut is uniquely situated to provide this output in a refreshing way (since most of what it makes is Markdown, most...