RELEASE @W-21741617@ Conducting v5.12.0 release

messages/config-command.md

@@ -117,3 +117,11 @@ Include unmodified rules in the rule override settings.
 # flags.include-unmodified-rules.description
 
 The default behavior of the config command is to not include the unmodified rules with their default values in the rule override settings (for the rules selected via the `–-rule-selector` flag). This default behavior prevents your configuration file from being unnecessarily large. If you want to include the unmodified rules, in addition to the modified rules, then specify this flag.
+
+# flags.no-suppressions.summary
+
+Exclude suppressions from the output configuration.
+
+# flags.no-suppressions.description
+
+When specified, the 'suppressions' field is not included in the configuration state. Since the 'suppressions' field may contain file or folder paths specific to a specific path, use this flag to make it easy to share your configuration state to be used for a different workspace.

messages/run-command.md

@@ -146,13 +146,29 @@ To output the results to multiple files, specify this flag multiple times. For e
 
 If you specify a file within a folder, such as `--output-file ./out/results.json`, the folder must already exist, or you get an error. If the file already exists, it's overwritten without prompting.
 
+# flags.include-fixes.summary
+
+Include fix data for violations when available.
+
+# flags.include-fixes.description
+
+When enabled, the output includes fix information for violations that have auto-fixes available. Each fix contains a code location and the replacement code. This flag may increase analysis time because engines must perform additional processing to compute fixes.
+
+# flags.include-suggestions.summary
+
+Include suggestion data for violations when available.
+
+# flags.include-suggestions.description
+
+When enabled, the output includes suggestion information for violations that have suggestions available. Each suggestion contains a code location and a message describing the suggested change.
+
 # flags.no-suppressions.summary
 
-Disable processing of inline suppression markers.
+Disable processing of inline and bulk suppression markers.
 
 # flags.no-suppressions.description
 
-By default, Code Analyzer processes inline suppression markers (code-analyzer-suppress and code-analyzer-unsuppress) found in your source code to filter out violations. Use this flag to ignore all suppression markers and report all violations.
+When specified, any inline suppression markers (code-analyzer-suppress, code-analyzer-suppress-line, and code-analyzer-suppress-next-line) found in targeted files are ignored and any suppressions supplied by your Code Analyzer configuration file are ignored so that no violations are suppressed by them.
 
 Note: If you have a `code-analyzer.yml` or `code-analyzer.yaml` configuration file with the `suppressions.disable_suppressions` field, the configuration file takes precedence over this flag.