Skip to content

Commit b590bae

Browse files
authored
Merge pull request #36592 from github/repo-sync
Repo sync
2 parents df69496 + d2d4e1a commit b590bae

File tree

3 files changed

+6
-3
lines changed

3 files changed

+6
-3
lines changed

content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Excluding folders and files from secret scanning
3-
intro: 'You can customize {% data variables.product.prodname_secret_scanning %} to exclude directories or files from analysis, by configuring a `secret_scanning.yml` file in your repository.'
3+
intro: 'You can customize {% data variables.product.prodname_secret_scanning %} to automatically close alerts for secrets found in specific directories or files by configuring a `secret_scanning.yml` file in your repository.'
44
permissions: '{% data reusables.permissions.secret-scanning-alerts %}'
55
shortTitle: Exclude folders and files
66
versions:
@@ -22,7 +22,7 @@ topics:
2222

2323
You may have a reason to commit a secret to a repository, such as when you want to provide a fake secret in documentation, or in an example application. In these scenarios, you can quickly dismiss the alert and document the reasons. However, there may be cases where you want to ignore a directory entirely to avoid creating false positive alerts at scale. For example, you might have a monolithic application with several integrations containing a file of dummy keys that could set off numerous false alerts to triage.
2424

25-
You can configure a `secret_scanning.yml` file to exclude directories from {% data variables.product.prodname_secret_scanning %}, including when you use push protection.
25+
You can configure a `secret_scanning.yml` file to automatically close alerts found in specific directories from {% data variables.product.prodname_secret_scanning %}, and exclude these directories included in push protection. These alerts are closed as "ignored by configuration".
2626

2727
## Excluding directories from {% data variables.secret-scanning.user_alerts %}
2828

@@ -36,7 +36,7 @@ You can configure a `secret_scanning.yml` file to exclude directories from {% da
3636
- "docs/**"
3737
```
3838
39-
This tells {% data variables.product.prodname_secret_scanning %} to ignore everything in the `docs` directory. You can use this example file as a template to add the files and folders you’d like to exclude from your own repositories.
39+
This tells {% data variables.product.prodname_secret_scanning %} to automatically close alerts for everything in the `docs` directory. You can use this example file as a template to add the files and folders you’d like to exclude from your own repositories.
4040

4141
You can also use special characters, such as `*` to filter paths. For more information about filter patterns, see [Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
4242

content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -362,6 +362,8 @@ To share feedback about {% data variables.product.prodname_copilot_chat_short %}
362362

363363
{% xcode %}
364364

365+
{% data reusables.copilot.xcode-chat-public-preview-note %}
366+
365367
## Prerequisites
366368

367369
To use {% data variables.product.prodname_copilot %} for Xcode, you must install the {% data variables.product.prodname_copilot %} for Xcode extension. See [AUTOTITLE](/copilot/configuring-github-copilot/installing-the-github-copilot-extension-in-your-environment).
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
> [!NOTE] {% data variables.product.prodname_copilot_chat_short %} in Xcode is in {% data variables.release-phases.public_preview %} and subject to change.

0 commit comments

Comments
 (0)