diff --git a/content/actions/how-tos/manage-runners/larger-runners/manage-larger-runners.md b/content/actions/how-tos/manage-runners/larger-runners/manage-larger-runners.md index 515fcdc6bbc4..acc10bb0f78b 100644 --- a/content/actions/how-tos/manage-runners/larger-runners/manage-larger-runners.md +++ b/content/actions/how-tos/manage-runners/larger-runners/manage-larger-runners.md @@ -191,7 +191,7 @@ You can control the maximum number of jobs allowed to run concurrently for speci > [!NOTE] > To use static IP addresses, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} -You can enable static IP addresses for {% data variables.actions.hosted_runner %}s. When you do this, the {% data variables.actions.hosted_runner %}s are assigned static IP address ranges. All IP addresses in the range assigned are usable and not in CIDR notation. By default, you can configure up to 10 different {% data variables.actions.hosted_runner %}s with IP ranges for your account. {% data reusables.actions.larger-runner-static-ip-contact-support %} +You can enable static IP addresses for {% data variables.actions.hosted_runner %}s. When you do this, the {% data variables.actions.hosted_runner %}s are assigned static IP address ranges. All IP addresses in the range assigned are usable. By default, you can configure up to 10 different {% data variables.actions.hosted_runner %}s with IP ranges for your account. {% data reusables.actions.larger-runner-static-ip-contact-support %} The number of available IP addresses in the assigned ranges does not restrict number of concurrent jobs specified for autoscaling. Within a runner pool, there is a load balancer which allows for high reuse of the IP addresses in the assigned ranges. This ensures your workflows can run concurrently at scale while each machine is assigned a static IP address. diff --git a/content/copilot/concepts/knowledge-bases.md b/content/copilot/concepts/knowledge-bases.md index 65e12a3ab3bf..9ce8a377e4e1 100644 --- a/content/copilot/concepts/knowledge-bases.md +++ b/content/copilot/concepts/knowledge-bases.md @@ -13,9 +13,13 @@ redirect_from: contentType: concepts --- -> [!TIP] If you're looking for a more flexible way to organize context for {% data variables.product.prodname_copilot_short %}, you can also try {% data variables.copilot.copilot_spaces %}. -> -> {% data variables.copilot.copilot_spaces_short %} let you combine code and free-text content—like transcripts or specs—and can be created by any {% data variables.product.prodname_copilot_short %} user, not just organization owners. They’re a good option for more focused or task-specific use cases. See [AUTOTITLE](/copilot/using-github-copilot/copilot-spaces/about-organizing-and-sharing-context-with-copilot-spaces). + + + + +>[!IMPORTANT] Beginning September 12, 2025, knowledge bases will be {% data variables.release-phases.retired %} and fully replaced by {% data variables.copilot.copilot_spaces %}. {% data variables.copilot.copilot_spaces_short %} let you combine code and free-text content—like transcripts or specs—and can be created by any {% data variables.product.prodname_copilot_short %} user, not just organization owners. They’re a good option for more focused or task-specific use cases. See [AUTOTITLE](/copilot/using-github-copilot/copilot-spaces/about-organizing-and-sharing-context-with-copilot-spaces). + + ## About knowledge bases @@ -26,4 +30,4 @@ When you ask a question in {% data variables.copilot.copilot_chat_short %} with ## Next steps * To learn how to create and manage knowledge bases, see [AUTOTITLE](/copilot/how-tos/context/creating-and-managing-copilot-knowledge-bases). -* To learn how to use knowledge bases in {% data variables.copilot.copilot_chat_short %}, see [AUTOTITLE](/copilot/how-tos/chat/asking-github-copilot-questions-in-github#asking-copilot-chat-questions-about-a-knowledge-base) and [AUTOTITLE](/copilot/how-tos/chat/asking-github-copilot-questions-in-your-ide#asking-a-question-about-a-knowledge-base). +* To learn how to use knowledge bases, see [AUTOTITLE](/copilot/how-tos/provide-context/use-knowledge-bases). diff --git a/content/copilot/how-tos/provide-context/create-knowledge-bases.md b/content/copilot/how-tos/provide-context/create-knowledge-bases.md index 7c5641756e1b..c96aa3a6dab3 100644 --- a/content/copilot/how-tos/provide-context/create-knowledge-bases.md +++ b/content/copilot/how-tos/provide-context/create-knowledge-bases.md @@ -25,6 +25,13 @@ redirect_from: - /copilot/how-tos/context/create-knowledge-bases contentType: how-tos --- + + + + +>[!IMPORTANT] Beginning September 12, 2025, knowledge bases will be {% data variables.release-phases.retired %} and fully replaced by {% data variables.copilot.copilot_spaces %}. {% data variables.copilot.copilot_spaces_short %} let you combine code and free-text content—like transcripts or specs—and can be created by any {% data variables.product.prodname_copilot_short %} user, not just organization owners. They’re a good option for more focused or task-specific use cases. See [AUTOTITLE](/copilot/using-github-copilot/copilot-spaces/about-organizing-and-sharing-context-with-copilot-spaces). + + Knowledge bases are a way to bring together Markdown documentation across one or more repositories. When you ask a question in {% data variables.copilot.copilot_chat_short %} with a knowledge base selected, {% data variables.product.prodname_copilot_short %} will search the knowledge base for relevant information and synthesize a response. diff --git a/content/copilot/how-tos/provide-context/use-knowledge-bases.md b/content/copilot/how-tos/provide-context/use-knowledge-bases.md index cf383216d40e..d681dc4b518b 100644 --- a/content/copilot/how-tos/provide-context/use-knowledge-bases.md +++ b/content/copilot/how-tos/provide-context/use-knowledge-bases.md @@ -12,6 +12,14 @@ redirect_from: contentType: how-tos --- + + + + +>[!IMPORTANT] Beginning September 12, 2025, knowledge bases will be {% data variables.release-phases.retired %} and fully replaced by {% data variables.copilot.copilot_spaces %}. {% data variables.copilot.copilot_spaces_short %} let you combine code and free-text content—like transcripts or specs—and can be created by any {% data variables.product.prodname_copilot_short %} user, not just organization owners. They’re a good option for more focused or task-specific use cases. See [AUTOTITLE](/copilot/using-github-copilot/copilot-spaces/about-organizing-and-sharing-context-with-copilot-spaces). + + + ## Introduction Knowledge bases are collections of documentation that you can use to provide context for your questions in {% data variables.copilot.copilot_chat %}. Knowledge bases are useful when you want to ask questions about a specific topic or set of topics, and you want the answers to be informed by the relevant documentation. diff --git a/data/reusables/actions/enterprise-github-hosted-runners.md b/data/reusables/actions/enterprise-github-hosted-runners.md index 3da2bbb88c67..2981388eb8ab 100644 --- a/data/reusables/actions/enterprise-github-hosted-runners.md +++ b/data/reusables/actions/enterprise-github-hosted-runners.md @@ -1,6 +1,6 @@ {% ifversion ghes %} > [!NOTE] -> {% data variables.product.prodname_dotcom %}-hosted runners are not currently supported on {% data variables.product.prodname_ghe_server %}. +> {% data variables.product.prodname_ghe_server %} users should use self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are **not** supported. {% endif %} diff --git a/src/secret-scanning/data/public-docs.yml b/src/secret-scanning/data/public-docs.yml index 9868b896fab8..e167d5ed29cd 100644 --- a/src/secret-scanning/data/public-docs.yml +++ b/src/secret-scanning/data/public-docs.yml @@ -2346,7 +2346,7 @@ ghes: '>3.8' isPublic: false isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: false base64Supported: false isduplicate: false @@ -2371,7 +2371,7 @@ ghec: '*' isPublic: false isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: false base64Supported: false isduplicate: false @@ -2852,7 +2852,7 @@ ghec: '*' isPublic: true isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: false base64Supported: false isduplicate: false @@ -3250,7 +3250,7 @@ ghes: '>=3.17' isPublic: true isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: '{% ifversion fpt or ghes %}false{% else %}true{% endif %}' base64Supported: false isduplicate: false @@ -3263,7 +3263,7 @@ ghes: '>=3.17' isPublic: true isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: '{% ifversion fpt or ghes %}false{% else %}true{% endif %}' base64Supported: false isduplicate: false @@ -4124,7 +4124,7 @@ ghec: '*' isPublic: false isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: false base64Supported: false isduplicate: false @@ -5301,7 +5301,7 @@ ghec: '*' isPublic: true isPrivateWithGhas: true - hasPushProtection: false + hasPushProtection: true hasValidityCheck: false base64Supported: false isduplicate: false diff --git a/src/secret-scanning/lib/config.json b/src/secret-scanning/lib/config.json index 7776708664e7..77aab81edb7e 100644 --- a/src/secret-scanning/lib/config.json +++ b/src/secret-scanning/lib/config.json @@ -1,5 +1,5 @@ { - "sha": "3262f345ee0cef143fdfdb12ee891ca782080c9f", - "blob-sha": "ae72750fe301854dee6ad18e16bfa6d8b55de962", + "sha": "2fd995a6f5c493aac019d1cf38312f2075a085fe", + "blob-sha": "dfaec435d708f9e3aeec2350b1326b010e266ace", "targetFilename": "code-security/secret-scanning/introduction/supported-secret-scanning-patterns" } \ No newline at end of file