🩹 [Patch]: Remove output access hints from logs

[Copilot]

Removes the output access hint text from the action logs to avoid confusion when the action is used directly or nested in another composite action. The output grouping and output content display remain unchanged.

• Fixes 🩹 [Patch]: Remove output access hints from logs #54

Changes

• Remove access-hint printing in scripts/outputs.ps1
• Simplify composite output test by removing access-pattern demo and help-text validation

Rationale

The access pattern differs for direct vs nested usage, so printed hints can be misleading. Removing the hint avoids confusion while still showing the output values.

[MariusStorhaug]

Try again

[MariusStorhaug]

@copilot Add a local action that we use in a test to see that the generated "output" suggestion is as expected. Find a way to automatically test that the output is correct.

[Copilot]

@copilot Add a local action that we use in a test to see that the generated "output" suggestion is as expected. Find a way to automatically test that the output is correct.

I've added comprehensive automated testing for the output suggestions:

Created:

1. Local composite action (.github/actions/test-composite/) that internally uses GitHub-Script
2. Test job ActionTestCompositeOutputs in TestWorkflow.yml that validates both direct and nested usage scenarios
3. Validation script (tests/validate-output-help-text.ps1) that programmatically tests the help text format

What the tests verify:

• ✅ Direct usage shows correct step ID: ${{ fromJson(steps.direct-test.outputs.result).DirectOutput }}
• ✅ Nested usage provides helpful placeholder: ${{ fromJson(steps.<your-step-id>.outputs.result).TestOutput1 }}
• ✅ Fallback scenario without step ID works correctly
• ✅ Both access patterns retrieve values successfully
• ✅ Help text format matches expected regex patterns

The tests will run automatically on every PR and catch any regressions. Commit: 78b146b

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• www.powershellgallery.com
  • Triggering command: /usr/bin/pwsh pwsh -Command Install-PSResource -Name PSScriptAnalyzer -TrustRepository -Scope CurrentUser (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR removes confusing output access hints from action logs. The hints showed how to access outputs using a specific pattern (${{ fromJson(steps.$env:GITHUB_ACTION.outputs.result).<outputName> }}), but this pattern varies depending on whether the action is used directly or nested within another composite action.

Changes:

• Removed output access hint text and decorative fence from scripts/outputs.ps1

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.