Skip to content

Commit 792df74

Browse files
committed
darwin updates
1 parent ce6583a commit 792df74

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Authentication to StackQL providers is done via environment variables source fro
1313
The following example demonstrate the use of the `stackql/setup-stackql` action in a GitHub Actions workflow, demonstrating how to use the action to install the `stackql` CLI and then use it to execute a StackQL query.
1414

1515
### GitHub Example
16-
Check the "Use GitHub Provider" step in [setup-stackql.yml](.github/workflows/setup-stackql.yml) for the working example, for more information on the GitHub provider for StackQL, see the [GitHub Provider Docs](https://registry.stackql.io/github).
16+
Check the "Use GitHub Provider" step in [setup-stackql-test.yml](.github/workflows/setup-stackql-test.yml) for the working example, for more information on the GitHub provider for StackQL, see the [GitHub Provider Docs](https://registry.stackql.io/github).
1717

1818
```yaml
1919
- name: setup StackQL
@@ -30,7 +30,7 @@ Check the "Use GitHub Provider" step in [setup-stackql.yml](.github/workflows/se
3030
```
3131
3232
### Google Example
33-
Check the "Use Google Provider" step in [setup-stackql.yml](.github/workflows/setup-stackql.yml) for the working example, for more information on the Google provider for StackQL, see the [Google Provider Docs](https://registry.stackql.io/google).
33+
Check the "Use Google Provider" step in [setup-stackql-test.yml](.github/workflows/setup-stackql-test.yml) for the working example, for more information on the Google provider for StackQL, see the [Google Provider Docs](https://registry.stackql.io/google).
3434
3535
```yaml
3636
- name: setup StackQL
@@ -46,14 +46,14 @@ Check the "Use Google Provider" step in [setup-stackql.yml](.github/workflows/se
4646
```
4747
4848
## Inputs
49-
- `use_wrapper` - (optional) Whether to install a wrapper to wrap subsequent calls of
49+
- __`use_wrapper`__ - (optional) Whether to install a wrapper to wrap subsequent calls of
5050
the `stackql` binary and expose its STDOUT, STDERR, and exit code as outputs
5151
named `stdout`, `stderr`, and `exitcode` respectively. Defaults to `false`.
5252

5353
## Outputs
5454
This action does not configure any outputs directly. However, when you set the `use_wrapper` input
5555
to `true`, the following outputs are available for subsequent steps that call the `stackql` binary:
5656

57-
- `stdout` - The STDOUT stream of the call to the `stackql` binary.
58-
- `stderr` - The STDERR stream of the call to the `stackql` binary.
59-
- `exitcode` - The exit code of the call to the `stackql` binary.
57+
- __`stdout`__ - The STDOUT stream of the call to the `stackql` binary.
58+
- __`stderr`__ - The STDERR stream of the call to the `stackql` binary.
59+
- __`exitcode`__ - The exit code of the call to the `stackql` binary.

0 commit comments

Comments
 (0)