Merge pull request #39705 from github/repo-sync

Repo sync

Author: docs-bot

content/code-security/code-scanning/managing-your-code-scanning-configuration/index.md

@@ -28,5 +28,6 @@ children:
   - /javascript-typescript-built-in-queries
   - /python-built-in-queries
   - /ruby-built-in-queries
+  - /rust-built-in-queries
   - /swift-built-in-queries
 ---

content/code-security/code-scanning/managing-your-code-scanning-configuration/rust-built-in-queries.md

@@ -0,0 +1,23 @@
+---
+title: Rust queries for CodeQL analysis
+shortTitle: Rust CodeQL queries
+intro: 'Explore the queries that {% data variables.product.prodname_codeql %} uses to analyze code written in Rust when you select the `default` or the `security-extended` query suite.'
+product: '{% data reusables.gated-features.codeql %}'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Code scanning
+  - CodeQL
+---
+
+{% data variables.product.prodname_codeql %} includes many queries for analyzing Rust code. {% data reusables.code-scanning.codeql-query-tables.query-suite-behavior %}
+
+## Built-in queries for Rust analysis
+
+{% data reusables.code-scanning.codeql-query-tables.codeql-version-info %}
+
+{% data reusables.code-scanning.codeql-query-tables.rust %}

content/code-security/codeql-cli/codeql-cli-manual/bqrs-interpret.md

@@ -102,7 +102,7 @@ all queries. It loads query help for /path/to/query.ql from the
 /path/to/query.md file. If this flag is not supplied the default
 behavior is to include help only for custom queries i.e. those in query
 packs which are not of the form \`codeql/\<lang\&rt;-queries\`. This
-option has no effect when passed to [codeql bqrs interpret](/code-security/codeql-cli/codeql-cli-manual/bqrs-interpret).
+option has no effect when passed to codeql bqrs interpret.
 
 #### `--sarif-include-query-help=<mode>`
 
@@ -117,7 +117,7 @@ queries i.e. those in query packs which are not of the form
 
 `never`: Do not include query help for any queries.
 
-This option has no effect when passed to [codeql bqrs interpret](/code-security/codeql-cli/codeql-cli-manual/bqrs-interpret).
+This option has no effect when passed to codeql bqrs interpret.
 
 Available since `v2.15.2`.
 
@@ -132,7 +132,7 @@ Available since `v2.18.1`.
 
 \[SARIF formats only] Place the rule object for each query under its
 corresponding QL pack in the `<run>.tool.extensions` property. This
-option has no effect when passed to [codeql bqrs interpret](/code-security/codeql-cli/codeql-cli-manual/bqrs-interpret).
+option has no effect when passed to codeql bqrs interpret.
 
 #### `--[no-]sarif-multicause-markdown`
 

content/code-security/codeql-cli/codeql-cli-manual/database-bundle.md

@@ -122,6 +122,9 @@ predicates.
 `fit`: Simply make sure the defined size limits for the disk cache are
 observed, deleting as many intermediates as necessary.
 
+`overlay`: Trim to just the data that will be useful when evaluating
+against an overlay.
+
 #### `--cleanup-upgrade-backups`
 
 Delete any backup directories resulting from database upgrades.

content/code-security/codeql-cli/codeql-cli-manual/database-cleanup.md

@@ -84,6 +84,9 @@ predicates.
 `fit`: Simply make sure the defined size limits for the disk cache are
 observed, deleting as many intermediates as necessary.
 
+`overlay`: Trim to just the data that will be useful when evaluating
+against an overlay.
+
 #### `--cleanup-upgrade-backups`
 
 Delete any backup directories resulting from database upgrades.

content/code-security/codeql-cli/codeql-cli-manual/database-create.md

@@ -286,6 +286,9 @@ predicates.
 `fit`: Simply make sure the defined size limits for the disk cache are
 observed, deleting as many intermediates as necessary.
 
+`overlay`: Trim to just the data that will be useful when evaluating
+against an overlay.
+
 #### `--cleanup-upgrade-backups`
 
 Delete any backup directories resulting from database upgrades.
@@ -311,7 +314,7 @@ configuration files that should work in most situations.
 
 \[Advanced] The directory in which the specified command should be
 executed. If this argument is not provided, the command is executed in
-the value of `--source-root` passed to [codeql database create](/code-security/codeql-cli/codeql-cli-manual/database-create), if one exists. If no `--source-root` argument is provided, the command is executed in the
+the value of `--source-root` passed to codeql database create, if one exists. If no `--source-root` argument is provided, the command is executed in the
 current working directory.
 
 #### `--no-run-unnecessary-builds`

content/code-security/codeql-cli/codeql-cli-manual/database-finalize.md

@@ -143,6 +143,9 @@ predicates.
 `fit`: Simply make sure the defined size limits for the disk cache are
 observed, deleting as many intermediates as necessary.
 
+`overlay`: Trim to just the data that will be useful when evaluating
+against an overlay.
+
 #### `--cleanup-upgrade-backups`
 
 Delete any backup directories resulting from database upgrades.

content/code-security/codeql-cli/codeql-cli-manual/database-init.md

@@ -264,7 +264,7 @@ will use all the values provided, in order. Extractor options specified
 using this command-line option are processed after extractor options
 given via `--extractor-options-file`.
 
-When passed to [codeql database init](/code-security/codeql-cli/codeql-cli-manual/database-init) or `codeql database begin-tracing`, the options will only be
+When passed to codeql database init or `codeql database begin-tracing`, the options will only be
 applied to the indirect tracing environment. If your workflow also makes
 calls to
 [codeql database trace-command](/code-security/codeql-cli/codeql-cli-manual/database-trace-command) then the options also need to be passed there if desired.
@@ -290,7 +290,7 @@ will use all the values provided, in order. Extractor options specified
 using this command-line option are processed before extractor options
 given via `--extractor-option`.
 
-When passed to [codeql database init](/code-security/codeql-cli/codeql-cli-manual/database-init) or `codeql database begin-tracing`, the options will only be
+When passed to codeql database init or `codeql database begin-tracing`, the options will only be
 applied to the indirect tracing environment. If your workflow also makes
 calls to
 [codeql database trace-command](/code-security/codeql-cli/codeql-cli-manual/database-trace-command) then the options also need to be passed there if desired.

content/code-security/codeql-cli/codeql-cli-manual/database-run-queries.md

@@ -37,7 +37,7 @@ the results subdirectory of the database directory.
 The results can later be converted to readable formats by [codeql database interpret-results](/code-security/codeql-cli/codeql-cli-manual/database-interpret-results), or query-for-query by with [codeql bqrs decode](/code-security/codeql-cli/codeql-cli-manual/bqrs-decode) or [codeql bqrs interpret](/code-security/codeql-cli/codeql-cli-manual/bqrs-interpret).
 
 If your queries produce results in a form that can be interpreted as
-source-code alerts, you may find [codeql database analyze](/code-security/codeql-cli/codeql-cli-manual/database-analyze) a more convenient way to run them. [codeql database analyze](/code-security/codeql-cli/codeql-cli-manual/database-analyze) combines [codeql database run-queries](/code-security/codeql-cli/codeql-cli-manual/database-run-queries) with [codeql database interpret-results](/code-security/codeql-cli/codeql-cli-manual/database-interpret-results) in a single step. In particular, [codeql database analyze](/code-security/codeql-cli/codeql-cli-manual/database-analyze) can produce output in the SARIF format, which can be used with an variety of alert viewers.
+source-code alerts, you may find [codeql database analyze](/code-security/codeql-cli/codeql-cli-manual/database-analyze) a more convenient way to run them. [codeql database analyze](/code-security/codeql-cli/codeql-cli-manual/database-analyze) combines codeql database run-queries with [codeql database interpret-results](/code-security/codeql-cli/codeql-cli-manual/database-interpret-results) in a single step. In particular, [codeql database analyze](/code-security/codeql-cli/codeql-cli-manual/database-analyze) can produce output in the SARIF format, which can be used with an variety of alert viewers.
 
 Alternatively, if you have only a single query to run, you might prefer
 [codeql query run](/code-security/codeql-cli/codeql-cli-manual/query-run), which can display human-readable output for quick inspection of results while you're debugging.

content/code-security/codeql-cli/codeql-cli-manual/database-trace-command.md

@@ -99,7 +99,7 @@ configuration files that should work in most situations.
 In addition to the specified command, run the main script for extractors
 that don't depend on tracing a build process. If you're constructing
 databases for several languages with `--db-cluster`, this option should
-be given to exactly one invocation of [codeql database trace-command](/code-security/codeql-cli/codeql-cli-manual/database-trace-command).
+be given to exactly one invocation of codeql database trace-command.
 
 #### `--[no-]use-build-mode`
 
@@ -144,7 +144,7 @@ given via `--extractor-options-file`.
 When passed to [codeql database init](/code-security/codeql-cli/codeql-cli-manual/database-init) or `codeql database begin-tracing`, the options will only be
 applied to the indirect tracing environment. If your workflow also makes
 calls to
-[codeql database trace-command](/code-security/codeql-cli/codeql-cli-manual/database-trace-command) then the options also need to be passed there if desired.
+codeql database trace-command then the options also need to be passed there if desired.
 
 See <https://codeql.github.com/docs/codeql-cli/extractor-options> for
 more information on CodeQL extractor options, including how to list the
@@ -170,7 +170,7 @@ given via `--extractor-option`.
 When passed to [codeql database init](/code-security/codeql-cli/codeql-cli-manual/database-init) or `codeql database begin-tracing`, the options will only be
 applied to the indirect tracing environment. If your workflow also makes
 calls to
-[codeql database trace-command](/code-security/codeql-cli/codeql-cli-manual/database-trace-command) then the options also need to be passed there if desired.
+codeql database trace-command then the options also need to be passed there if desired.
 
 See <https://codeql.github.com/docs/codeql-cli/extractor-options> for
 more information on CodeQL extractor options, including how to list the