feat: Update inputs for egress policy and additional checkout options#64
Merged
rbarker-dev merged 2 commits intoMay 19, 2026
Merged
Conversation
Signed-off-by: Roger Barker <roger.barker@swirldslabs.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR expands the composite action and its test workflow to support configurable Harden Runner egress policy, additional repository checkout customization, and extra outputs/documentation to improve consumer visibility.
Changes:
- Added an
egress-policyinput and a new CI job intended to validate egress-policy configuration. - Added checkout customization inputs (
checkout-path,checkout-persist) and threaded them through toactions/checkout. - Added/updated action outputs and README documentation (including
checkout-pathand Node registry reporting).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
README.md |
Documents the new Harden Runner/checkout inputs and adds new output descriptions and examples. |
action.yml |
Implements new inputs and wires them into Harden Runner + checkout; introduces new outputs. |
.github/workflows/test.yml |
Updates the integration test job to pass/print new inputs/outputs and adds a new egress-policy test job. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Roger Barker <roger.barker@swirldslabs.com>
andrewb1269
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces several enhancements and new configuration options for the GitHub Actions workflow and composite action, focusing on improved security, flexibility in repository checkout, and better output reporting. The most significant changes are the addition of configurable egress policy for security hardening, expanded checkout options, and improved documentation and outputs for consumers of the action.
Security and Egress Policy:
egress-policyinput to the composite action and workflow, allowing users to set the Step Security Harden Runner to eitheraudit(default) orblockmode for network egress control. A new job was added to test this input, and documentation was updated to explain its usage. [1] [2] [3] [4] [5] [6] [7]Repository Checkout Enhancements:
checkout-path(specifies the directory to checkout into, defaulting to.) andcheckout-persist(controls whether credentials are persisted, defaulting totrue). These are now passed to the checkout step and documented. [1] [2] [3] [4]Output Improvements:
checkout-path(reports the checkout directory) andnode-registry-url(reports the Node.js registry used). Workflow steps were updated to display these outputs for easier debugging and traceability. [1] [2] [3] [4] [5]Documentation Updates:
README.mdto document the new inputs and outputs, including detailed tables and usage examples for egress policy, checkout options, and Node.js registry configuration. [1] [2] [3] [4] [5] [6]These changes provide improved security configurability, greater flexibility for repository checkout, and clearer outputs and documentation for users of the action.
Related Issue(s)