Repo sync

content/billing/concepts/product-billing/git-lfs.md

@@ -47,10 +47,21 @@ category:
 
 ## How use of {% data variables.large_files.product_name_short %} is measured
 
-Each {% data variables.product.github %} account receives a quota of free bandwidth and storage for {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Any usage beyond the included amounts is billed to your account. 
+Previously, {% data variables.large_files.product_name_short %} billing used pre-paid data packs. These have been removed and replaced with metered billing and you only pay for what you actually use.
+
+Each {% data variables.product.github %} account includes a quota of free bandwidth and storage for {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). If you exceed this quota, what happens next depends on your {% data variables.large_files.product_name_short %} budget setting:
+
+* **Budget set to $0**: You are not charged for overages, but {% data variables.large_files.product_name_short %} usage is blocked for the rest of the calendar month. Usage resets on the first of the next month.
+* **Budget deleted**: There is no spending limit, and you are billed for all usage beyond the free quota.
 
 * **Bandwidth:** Your free quota resets at the start of each billing cycle. 
-* **Storage:** Charges accrue continuously throughout the month based on hourly usage. Your accrued storage total resets to zero at the begining of each billing cycle.
+* **Storage:** Charges accrue continuously throughout the month based on hourly usage. Your accrued storage total resets to zero at the beginning of each billing cycle.
+
+{% data variables.large_files.product_name_short %} storage is calculated based on all {% data variables.large_files.product_name_short %} objects associated with a repository, regardless of when they were uploaded. Storage usage is only zero when no {% data variables.large_files.product_name_short %} objects are associated with the repository.
+
+If you delete {% data variables.large_files.product_name_short %} objects partway through a calendar month, the storage usage for that month is not recalculated. Storage resets on the first of the following month.
+
+To learn how to reduce your usage going forward, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage).
 
 Working in a public or private repository with {% data variables.large_files.product_name_short %}:
 
@@ -117,12 +128,18 @@ For example, if you use 1 GiB above what is included for free for the first 15 d
 
 In this example, you would pay for 1.5 GiB of additional storage for the month of April.
 
+## Included usage alerts for {% data variables.large_files.product_name_short %}
+
+You can receive email notifications when your included {% data variables.large_files.product_name_short %} usage reaches 90% and 100% during a billing period. See [AUTOTITLE](/billing/concepts/product-billing/git-lfs#how-use-of-git-lfs-is-measured) to learn more about why you may be receiving the notification.
+
+For more information, including on how to disable them, see [AUTOTITLE](/billing/concepts/budgets-and-alerts#included-usage-alerts).
+
+If you’d like to continue using LFS storage and bandwidth for the current calendar month, you can [adjust the account’s budget to allow overages](/billing/concepts/product-billing/git-lfs#paying-for-additional-git-lfs-use). On your next billing date, you’ll be charged for the actual usage in the previous calendar month.
+
 ## Managing your budget for {% data variables.large_files.product_name_short %}
 
 {% data reusables.billing.default-over-quota-behavior %}
 
-You can also receive email notifications when your included {% data variables.large_files.product_name_short %} usage reaches 90% and 100% during a billing period. For more information, see [AUTOTITLE](/billing/concepts/budgets-and-alerts#included-usage-alerts).
-
 ## Further reading
 
 * [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)

content/code-security/concepts/security-at-scale/about-enabling-security-features-at-scale.md

@@ -6,6 +6,10 @@ versions:
   feature: security-configurations
 redirect_from:
   - /code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale
+  - /code-security/concepts/security-at-scale/about-security-configurations
+  - /admin/managing-code-security/securing-your-enterprise/about-security-configurations
+  - /code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/choosing-a-security-configuration-for-your-repositories
+  - /code-security/concepts/security-at-scale/choosing-a-security-configuration-for-your-repositories
 contentType: concepts
 ---
 

content/copilot/concepts/context/repository-indexing.md

@@ -1,7 +1,7 @@
 ---
-title: Indexing repositories for GitHub Copilot Chat
+title: Indexing repositories for GitHub Copilot
 shortTitle: Repository indexing
-intro: '{% data variables.copilot.copilot_chat %} improves responses to questions about code by indexing your repositories.'
+intro: '{% data variables.product.prodname_copilot_short %} improves responses by indexing your repositories.'
 versions:
   feature: copilot
 redirect_from:
@@ -20,19 +20,30 @@ category:
 
 ## Benefit of indexing repositories
 
-{% data variables.copilot.copilot_chat_short %}'s ability to answer natural language questions in a repository context is optimized when the semantic code search index for the repository is up to date.
+{% data variables.product.prodname_copilot_short %}'s ability to answer natural language questions and complete tasks in a repository context is optimized when the semantic code search index for the repository is up to date.
 
-When you start a conversation with {% data variables.copilot.copilot_chat_short %} that has a repository context, the repository is automatically indexed to improve context-enriched answers to your questions about the code's structure and logic in {% data variables.product.github %} and {% data variables.product.prodname_vscode %}. For example, you can ask **“How does this repo manage HTTP requests and responses?”** and {% data variables.copilot.copilot_chat_short %} will reference relevant sections of your code to deliver an informed answer.
+**{% data variables.product.prodname_copilot_short %} will not use your indexed repository for model training.**
+
+## Semantic code search in {% data variables.copilot.copilot_chat_short %}
 
-**{% data variables.copilot.copilot_chat_short %} will not use your indexed repository for model training.**
+When you start a conversation with {% data variables.copilot.copilot_chat_short %} that has a repository context, the repository is automatically indexed to improve context-enriched answers to your questions about the code's structure and logic in {% data variables.product.github %} and {% data variables.product.prodname_vscode %}. For example, you can ask **“How does this repo manage HTTP requests and responses?”** and {% data variables.copilot.copilot_chat_short %} will reference relevant sections of your code to deliver an informed answer.
 
 For more information on how to ask questions, see [AUTOTITLE](/copilot/using-github-copilot/asking-github-copilot-questions-in-github).
 
+## Semantic code search in {% data variables.copilot.copilot_coding_agent %}
+
+{% data variables.copilot.copilot_coding_agent %} uses semantic code search to find relevant code based on meaning, rather than relying solely on exact text matches with tools like `grep`. When the agent doesn't know the precise names or patterns to search for, semantic code search helps it locate the right code faster. No configuration is required—the agent automatically uses semantic code search when appropriate.
+
+For more information about {% data variables.copilot.copilot_coding_agent %}, see [AUTOTITLE](/copilot/concepts/agents/coding-agent/about-coding-agent).
+
 ## About index creation and use
 
 Indexing runs in the background and initial indexing can take up to 60 seconds for a large repository. Once a repository has been indexed for the first time, re-indexing is much quicker and the index will typically be automatically updated to include the latest changes within seconds of you starting a new conversation.
 
-Once an index has been created for a repository, {% data variables.copilot.copilot_chat_short %} uses it to answer questions asked by any {% data variables.product.prodname_copilot_short %} user in {% data variables.product.github %} and {% data variables.product.prodname_vscode %}.
+Once an index has been created for a repository, it can be used by:
+
+* {% data variables.copilot.copilot_chat_short %} in {% data variables.product.github %} and {% data variables.product.prodname_vscode %}
+* {% data variables.copilot.copilot_coding_agent %}
 
 > [!TIP] There is no limit to how many repositories you can index.
 

content/copilot/responsible-use/copilot-coding-agent.md

@@ -13,7 +13,7 @@
   - Responsible use
 ---
 
 ## About {% data variables.copilot.copilot_coding_agent %} on {% data variables.product.prodname_dotcom_the_website %}
 
 {% data variables.copilot.copilot_coding_agent %} is an autonomous and asynchronous software development agent integrated into {% data variables.product.github %}. The agent can pick up a task from an issue or from {% data variables.copilot.copilot_chat_short %}, create a pull request, and then iterate on the pull request in response to comments.
 
@@ -75,7 +75,9 @@
 
 ### Customize your experience with additional context
 
-{% data variables.copilot.copilot_coding_agent %} leverages your prompt, comments and the repository’s code as context when generating suggested changes. To enhance Copilot’s performance, consider implementing custom Copilot instructions to help the agent better understand your project and how to build, test and validate its changes. For more information, see "Add custom instructions to your repository" in [AUTOTITLE](/copilot/tutorials/coding-agent/best-practices#adding-custom-instructions-to-your-repository).
+{% data variables.copilot.copilot_coding_agent %} leverages your prompt, comments and the repository’s code as context when generating suggested changes. The agent also has access to semantic code search, which helps it find relevant code based on meaning rather than just exact text matches, allowing it to complete tasks faster.
+
+To enhance {% data variables.product.prodname_copilot_short %}’s performance, consider implementing custom {% data variables.product.prodname_copilot_short %} instructions to help the agent better understand your project and how to build, test and validate its changes. For more information, see "Add custom instructions to your repository" in [AUTOTITLE](/copilot/tutorials/coding-agent/best-practices#adding-custom-instructions-to-your-repository).
 
 For information about other customizations for {% data variables.copilot.copilot_coding_agent %}, see:
 

content/copilot/tutorials/coding-agent/get-the-best-results.md

@@ -31,6 +31,9 @@ category:
 * Complete acceptance criteria on what a good solution looks like (for example, should there be unit tests?).
 * Directions about which files need to be changed.
 
+> [!TIP]
+> {% data variables.copilot.copilot_coding_agent %} has the ability to search your codebase, including semantic code search, which helps it find relevant code based on meaning rather than just exact text matches. Even if you don't specify exact file paths in a task, the agent can often discover the right code on its own.
+
 If you pass a task to {% data variables.product.prodname_copilot_short %} by assigning an issue, it's useful to think of the issue you assign to {% data variables.product.prodname_copilot_short %} as a prompt. Consider whether the issue description is likely to work as an AI prompt, and will enable {% data variables.product.prodname_copilot_short %} to make the required code changes.
 
 ## Choosing the right type of tasks to give to {% data variables.product.prodname_copilot_short %}

content/issues/tracking-your-work-with-issues/using-issues/adding-and-managing-issue-fields.md

@@ -82,5 +82,6 @@ For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/usi
 
 Issue fields have full REST and GraphQL API support. You can automate field management, set values programmatically, and integrate with external tools.
 
-- **Managing fields**: Create, update, and delete organization-level fields. See the [Organization issue fields REST API](/rest/orgs/issue-fields).
-- **Using fields**: Get, set, and clear field values on individual issues. See the [Issue field values REST API](/rest/issues/issue-field-values).
+* **Managing fields**: Create, update, and delete organization-level fields. See the [Organization issue fields REST API](/rest/orgs/issue-fields).
+* **Using fields**: Get, set, and clear field values on individual issues. See the [Issue field values REST API](/rest/issues/issue-field-values).
+* **GraphQL**: Issue field types and mutations are also available via GraphQL. See the [`IssueFields` union](/graphql/reference/unions#issuefields), [issue field objects](/graphql/reference/objects#issuefieldtext) (such as `IssueFieldText`, `IssueFieldSingleSelect`, `IssueFieldNumber`, and `IssueFieldDate`), and [mutations](/graphql/reference/mutations#createissuefield) (such as `createIssueField`, `updateIssueField`, and `setIssueFieldValue`).