Skip to content

Commit f761241

Browse files
author
Simon Engledew
committed
Remove output from README
As this is an advanced usage it makes more sense to work to getting this included in the documentation instead.
1 parent c87f302 commit f761241

File tree

2 files changed

+1
-19
lines changed

2 files changed

+1
-19
lines changed

.github/workflows/codeql.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ jobs:
1919
with:
2020
languages: javascript
2121
config-file: ./.github/codeql/codeql-config.yml
22-
# example from README.md
22+
# confirm steps.init.outputs.codeql-path points to the codeql binary
2323
- name: Print CodeQL Version
2424
run: ${{steps.init.outputs.codeql-path}} version --format=json
2525
- uses: ./analyze

README.md

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -125,24 +125,6 @@ By default, this will override any queries specified in a config file. If you wi
125125
queries: +<local-or-remote-query>,<another-query>
126126
```
127127

128-
### Calling CodeQL Directly
129-
130-
The `init` action makes the path to CodeQL available as the output `codeql-path`.
131-
132-
With this you can access the `codeql` binary:
133-
134-
<!-- this example is run via .github/workflows/codeql.yml -->
135-
```yaml
136-
- name: Initialize CodeQL
137-
uses: github/codeql-action/init@v1
138-
id: init
139-
with:
140-
languages: javascript
141-
142-
- name: Print CodeQL Version
143-
run: ${{steps.init.outputs.codeql-path}} version --format=json
144-
```
145-
146128
## Troubleshooting
147129

148130
Read about [troubleshooting code scanning](https://help.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning).

0 commit comments

Comments
 (0)