3rd attempt for reports

Author: psjamesp

.github/workflows/pester_reports.yml

@@ -1,126 +1,10 @@
-- name: pester-tests-report
-  # You may pin to the exact commit or the version.
-  # uses: zyborg/pester-tests-report@bb711b31e93f78f7423086d57f81928325829765
-  uses: zyborg/pester-tests-report@v1.5.0
-  with:
-    # Path to the test results file which will be used to generate
-a report.  If this path is provided, it will override the
-execution of all Pester tests, so the **`include_paths`**
-input and all other inputs that drive the test invocation behavior
-will be ignored. Instead a report will be generated based on the
-results stored in the file pointed to by this path.
-At this time, the only test results format supported is the
-NUnit 2.5 Tests results XML schema.
-
-    test_results_path: # optional
-    # Comma-separated list of test full names, or with `-like` wildcards, to restrict which tests are resolved.  The default is to include every test discovered matching the other input parameters.
-    full_names_filters: # optional
-    # Comma-separated list of one or more test files or directories
-that contain test files, relative to the root of the project.
-This path is optional and defaults to the project root,
-in which case all tests script across the entire project tree
-will be discovered.  A test script is identified by the
-filename pattern `*.Tests.ps1`.
-This parameter is _ignored_ if the **`test_results_path`**
-parameter is also provided.
-
-    include_paths: # optional
-    # Comma-separated list of one or more test files or directories
-that contain test files, relative to the root of the project,
-that will be excluded from the list fo auto-discovered tests.
-This parameter is _ignored_ if the **`test_results_path`**
-parameter is also provided.
-
-    exclude_paths: # optional
-    # Comma-separated list of tags to include for testing.
-This parameter is _ignored_ if the **`test_results_path`**
-parameter is also provided.
-
-    include_tags: # optional
-    # Comma-separated list of tags to exclude for testing.
-This parameter is _ignored_ if the **`test_results_path`**
-parameter is also provided.
-
-    exclude_tags: # optional
-    # Optionally specify the level of output detail for the test results.
-May be one of: `none`, `Minimal`, `normal`, `detailed`, `diagnostic`
-The default is `normal`.
-
-    output_level: # optional
-    # The name of the report object that will be attached to the
-Workflow Run.  Defaults to the name `TEST_RESULTS_<datetime>`
-where `<datetime>` is in the form `yyyyMMdd_hhmmss`.
-
-    report_name: # optional
-    # The title of the report that will be embedded in the report
-itself, which defaults to the same as the `report_name` input.
-
-    report_title: # optional
-    # GITHUB_TOKEN to authenticate against API calls to attach
-report to Workflow Run.
-
-    github_token: # optional
-    # If true, will skip attaching the Tests Result report to
-the Workflow Run using a Check Run.  Useful if you just
-want to produce a Gist-based report via the `gist_name`
-and `gist_token` input parameters.
-
-    skip_check_run: # optional
-    # If this value is specifed, the Test Results Report will be
-attached as a version of a Gist under the name of this input.
-The `gist_token` input is also required to use this feature.
-
-    gist_name: # optional
-    # If specified, the Test Report Gist will also include an adjacent
-badge rendered with the status of the associated Test Report and
-and label content of this input.  In addition to any static text
-you can provide _escape tokens_ of the form `%name%` where name
-can be the name of any field returned from a Pester Result, such
-as `ExecutedAt` or `Result`.  If you want a literal percent, just
-specify an empty name as in `%%`.
-
-    gist_badge_label: # optional
-    # If Gist badge generation is enabled by providing a value for the
-`gist_badge_label` input, this input allows you to override the
-default message on the badge, which is equivalent to the the
-Pester Result `Status` such as `Failed` or `Passed`.  As with the
-label input, you can specify escape tokens in addition to literal
-text.  See the label input description for more details.
-
-    gist_badge_message: # optional
-    # GitHub OAuth/PAT token to be used for accessing Gist to store
-test results report. The integrated GITHUB_TOKEN that is normally
-accessible during a Workflow does not include read/write permissions
-to associated Gists, therefore a separate token is needed.
-You can control which account is used to actually store the state by
-generating a token associated with the target account.
-
-    gist_token: # optional
-    # Comma-separated list of one or more directories to scan for code
-coverage, relative to the root of the project. Will include all .ps1
-and .psm1 files under these directories recursively.
-
-    coverage_paths: # optional
-    # The name of the code coverage report object that will be attached
-to the Workflow Run.  Defaults to the name
-`COVERAGE_RESULTS_<datetime>` where `<datetime>` is in the form
-`yyyyMMdd_hhmmss`.
-
-    coverage_report_name: # optional
-    # The title of the code coverage report that will be embedded in the
-report itself, which defaults to the same as the
-`code_coverage_report_name` input.
-
-    coverage_report_title: # optional
-    # If true, will attach the coverage results to the gist specified in
-`gist_name`.
-
-    coverage_gist: # optional
-    # If specified, the Test Report Gist will also include an adjacent
-badge rendered with the percentage of the associated Coverage Report
-and label content of this input.
-
-    coverage_gist_badge_label: # optional
-    # If true, will cause the step to fail if one or more tests fails.
-
-    tests_fail_step: # optional
+name: Pester
+on:
+  push:
+    branches: [ master ]
+jobs:
+  test-pwsh:
+    runs-on: windows-latest
+    steps:
+    - name: pester-tests-report
+    - uses: zyborg/pester-tests-report@v1.5.0