jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 11:26:57 -05:00
Code Issues Projects Releases Wiki Activity

Fix trailing spaces in content and data (#37904)

Browse Source
This commit is contained in:
Grace Park
2023-06-23 10:45:10 -07:00
committed by GitHub
parent 07dcb8c294
commit cbda3f2434
369 changed files with 642 additions and 641 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/code-security/codeql-cli/codeql-cli-reference/about-codeql-packs.md
View File

@@ -75,7 +75,7 @@ The following properties are supported in `qlpack.yml` files.
#### `name`
- Required by all packs.
- Required by all packs.
- Defines the scope of the pack, where the {% data variables.product.prodname_codeql %} pack is published, and the name of the pack defined using alphanumeric characters and hyphens. It must be unique as {% data variables.product.prodname_codeql %} cannot differentiate between {% data variables.product.prodname_codeql %} packs with identical names. Use the pack name to specify queries to run using `database analyze` and to define dependencies between {% data variables.product.prodname_codeql %} packs (see examples below). For example:
```yaml
name: octo-org/security-queries
@@ -155,7 +155,7 @@ The following properties are supported in `qlpack.yml` files.
```
#### `license`
- Optional.
- Optional.
- Defines metadata that will be displayed on the packaging search page in the packages section of the account that the {% data variables.product.prodname_codeql %} pack is published to. For a list of allowed licenses, see [SPDX License List](https://spdx.org/licenses/) in the SPDX Specification. For example:
```yaml
license: MIT
@@ -169,7 +169,7 @@ The following properties are supported in `qlpack.yml` files.
```
#### `libraryPathDependencies`
- Optional, deprecated. Use the `dependencies` property instead.
- Optional, deprecated. Use the `dependencies` property instead.
- Previously used to define the names of any {% data variables.product.prodname_codeql %} packs that this {% data variables.product.prodname_codeql %} pack depends on, as an array. This gives the pack access to any libraries, database schema, and query suites defined in the dependency. For example:
```yaml
libraryPathDependencies: codeql/javascript-all

2
content/code-security/codeql-cli/using-the-codeql-cli/creating-and-working-with-codeql-packs.md
View File

@@ -84,7 +84,7 @@ This command downloads all dependencies to the shared cache on the local disk.
{% note %}
**Notes:**
**Notes:**
- Running the `codeql pack add` and `codeql pack install` commands will generate or update the `codeql-pack.lock.yml` file. This file should be checked-in to version control. The `codeql-pack.lock.yml` file contains the precise version numbers used by the pack. For more information, see "[About codeql-pack.lock.yml files](/code-security/codeql-cli/codeql-cli-reference/about-codeql-packs#about-codeql-pack-lock)."

6
content/code-security/codeql-cli/using-the-codeql-cli/creating-codeql-databases.md
View File

@@ -55,7 +55,7 @@ You must specify:
| Java{% ifversion codeql-kotlin-beta %}/Kotlin{% endif %} | `java`
| JavaScript/TypeScript | `javascript`
| Python | `python`
| Ruby | `ruby` {% ifversion codeql-swift-beta %}
| Ruby | `ruby` {% ifversion codeql-swift-beta %}
| Swift | `swift` {% endif %}
{% data reusables.code-scanning.beta-kotlin-or-swift-support %}
@@ -213,7 +213,7 @@ The following examples are designed to give you an idea of some of the build com
{% ifversion codeql-swift-beta %}
- Swift project built from an Xcode project or workspace. By default, the largest Swift target is built:
It's a good idea to ensure that the project is in a clean state and that there are no build artefacts available.
```
@@ -233,7 +233,7 @@ The following examples are designed to give you an idea of some of the build com
codeql database create -l swift -c "xcodebuild build -target your-target" swift-database
```
You can pass the `archive` and `test` options to `xcodebuild`. However, the standard `xcodebuild` command is recommended as it should be the fastest, and should be all that CodeQL requires for a successful scan.
You can pass the `archive` and `test` options to `xcodebuild`. However, the standard `xcodebuild` command is recommended as it should be the fastest, and should be all that CodeQL requires for a successful scan.
- Swift project built using a custom build script: