Skip to content

Commit

Permalink
Merge pull request #191 from cclauss/patch-1
Browse files Browse the repository at this point in the history
README.md: uses: actions/checkout@v4
  • Loading branch information
jmealo authored Mar 28, 2024
2 parents 59e89a8 + 85c8182 commit 0444a07
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ jobs:
env:
API_PORT: 1212
steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v4
- uses: JarvusInnovations/background-action@v1
name: Bootstrap System Under Test (SUT)
with:
Expand All @@ -54,7 +54,7 @@ jobs:
# This will allow you to monitor the progress live

log-output-resume: stderr
# Eliminates previosuly output stderr log entries from post-run output
# Eliminates previously output stderr log entries from post-run output

wait-for: 5m

Expand Down Expand Up @@ -85,7 +85,7 @@ jobs:

### wait-on

`background-action` leverages the handy [wait-on](https://www.npmjs.com/package/wait-on) package to control flow. You can pass any number of resources in the `wait-on` configuration parameter seperated by commas or newlines. For advanced use cases, such as: client-side SSL certs, authorization, proxy configuration and/or custom http headers you can provide a JSON serialized configuration object that matches [wait-on's node.js api usage](https://www.npmjs.com/package/wait-on#nodejs-api-usage).
`background-action` leverages the handy [wait-on](https://www.npmjs.com/package/wait-on) package to control flow. You can pass any number of resources in the `wait-on` configuration parameter separated by commas or newlines. For advanced use cases, such as: client-side SSL certs, authorization, proxy configuration and/or custom http headers you can provide a JSON serialized configuration object that matches [wait-on's node.js api usage](https://www.npmjs.com/package/wait-on#nodejs-api-usage).

#### Resource Types

Expand Down

0 comments on commit 0444a07

Please sign in to comment.