From 90f5951e3e1ae5e97dc3085fec729edc34b9bba8 Mon Sep 17 00:00:00 2001 From: docs-bot <77750099+docs-bot@users.noreply.github.com> Date: Tue, 5 Aug 2025 23:54:38 -0700 Subject: [PATCH 1/4] Sync secret scanning data (#56993) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- src/secret-scanning/data/public-docs.yml | 22 ++++++++++++++++++++++ src/secret-scanning/lib/config.json | 4 ++-- 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/src/secret-scanning/data/public-docs.yml b/src/secret-scanning/data/public-docs.yml index 9e3d647dd188..44751b2bc2bc 100644 --- a/src/secret-scanning/data/public-docs.yml +++ b/src/secret-scanning/data/public-docs.yml @@ -93,6 +93,28 @@ hasPushProtection: true hasValidityCheck: false isduplicate: false +- provider: Airtable + supportedSecret: Airtable API Key + secretType: airtable_api_key + versions: + fpt: '*' + ghec: '*' + isPublic: false + isPrivateWithGhas: true + hasPushProtection: false + hasValidityCheck: false + isduplicate: false +- provider: Airtable + supportedSecret: Airtable Personal Access Token + secretType: airtable_personal_access_token + versions: + fpt: '*' + ghec: '*' + isPublic: false + isPrivateWithGhas: true + hasPushProtection: false + hasValidityCheck: false + isduplicate: false - provider: Aiven supportedSecret: Aiven Auth Token secretType: aiven_auth_token diff --git a/src/secret-scanning/lib/config.json b/src/secret-scanning/lib/config.json index 0a3891776603..e46e9a992b23 100644 --- a/src/secret-scanning/lib/config.json +++ b/src/secret-scanning/lib/config.json @@ -1,5 +1,5 @@ { - "sha": "1a082834369ed04963911ef06c4a0de0cf1755a0", - "blob-sha": "70a236d2f851f211cfff51c0976d31a48677503c", + "sha": "57f562211d056bd03227a2288da3014cb6e0c7d3", + "blob-sha": "e18e517f8baea4b5e4e955053da7b31cdf1653e6", "targetFilename": "code-security/secret-scanning/introduction/supported-secret-scanning-patterns" } \ No newline at end of file From 2ab0dea4fa5f34c2e24c47dbc43d0677753d9f62 Mon Sep 17 00:00:00 2001 From: Tadas Labudis Date: Wed, 6 Aug 2025 08:57:26 +0100 Subject: [PATCH 2/4] Create duplicating-an-issue.md (#56412) Co-authored-by: Lukasz Warchol Co-authored-by: Kevin Heis Co-authored-by: Renee Xu Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../duplicating-an-issue.md | 30 +++++++++++++++++++ .../administering-issues/index.md | 1 + data/features/duplicating-an-issue.yml | 6 ++++ 3 files changed, 37 insertions(+) create mode 100644 content/issues/tracking-your-work-with-issues/administering-issues/duplicating-an-issue.md create mode 100644 data/features/duplicating-an-issue.yml diff --git a/content/issues/tracking-your-work-with-issues/administering-issues/duplicating-an-issue.md b/content/issues/tracking-your-work-with-issues/administering-issues/duplicating-an-issue.md new file mode 100644 index 000000000000..4ae61cff8ada --- /dev/null +++ b/content/issues/tracking-your-work-with-issues/administering-issues/duplicating-an-issue.md @@ -0,0 +1,30 @@ +--- +title: Duplicating an issue +intro: 'To quickly create a similar issue, you can duplicate an existing open issue into the same repository or a different one.' +versions: + feature: duplicating-an-issue +topics: + - Issues +shortTitle: Duplicate an issue +--- + +To duplicate an open issue, you must have triage access to the repository that contains the original issue and to the destination repository. The destination repository must allow blank issues. See [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization). + +When you duplicate an issue, a new issue is created with the original issue’s title, description, assignees, type, labels, milestones, and projects prefilled, as long as those fields exist or are available in the destination repository. Labels and milestones are retained if they are present in the target repository, with labels matching by name and milestones matching by both name and due date. The original issue remains unchanged. + +People or teams mentioned in the original issue will not receive notifications about the duplication. The new issue will have its own URL and can be edited before being created. If you attempt to duplicate an issue to a repository where you do not have triage access, the option will not be available. + +## Duplicating an open issue + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} + +1. In the list of issues, click the issue you'd like to duplicate. +1. In the right sidebar, click **Duplicate issue**. +1. In the **Choose a repository** dropdown, select the destination repository. You can choose the same repository or a different one. +1. Edit the prefilled issue details as needed. +1. Click **Create issue**. + +## Further reading + +* [AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues) diff --git a/content/issues/tracking-your-work-with-issues/administering-issues/index.md b/content/issues/tracking-your-work-with-issues/administering-issues/index.md index d0d1614bf148..18778d82af67 100644 --- a/content/issues/tracking-your-work-with-issues/administering-issues/index.md +++ b/content/issues/tracking-your-work-with-issues/administering-issues/index.md @@ -13,4 +13,5 @@ children: - /transferring-an-issue-to-another-repository - /closing-an-issue - /deleting-an-issue + - /duplicating-an-issue --- diff --git a/data/features/duplicating-an-issue.yml b/data/features/duplicating-an-issue.yml new file mode 100644 index 000000000000..1db5956b43d0 --- /dev/null +++ b/data/features/duplicating-an-issue.yml @@ -0,0 +1,6 @@ +# Reference: #18759 +# Versions for which duplicating issues is available +versions: + fpt: '*' + ghec: '*' + ghes: '>3.18' From 2a3908a1c6d9d32ca8277980df9763865dd18ef1 Mon Sep 17 00:00:00 2001 From: mc <42146119+mchammer01@users.noreply.github.com> Date: Wed, 6 Aug 2025 09:19:31 +0100 Subject: [PATCH 3/4] Delegated bypass and alert closure requests can be reviewed programmatically (#56865) Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com> --- .../managing-requests-to-bypass-push-protection.md | 4 ++++ .../enabling-delegated-alert-dismissal-for-secret-scanning.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection.md b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection.md index c6af1d5c0dcc..3a42dc9391b4 100644 --- a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection.md +++ b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection.md @@ -21,6 +21,10 @@ shortTitle: Manage bypass requests When enabling delegated bypass for push protection, organization owners or repository administrators decide which {% ifversion push-protection-bypass-fine-grained-permissions %}individuals, {% endif %}roles or teams can review (approve or deny) requests to bypass push protection. +>[!NOTE] +> You can also use {% data variables.product.prodname_github_apps %} with fine-grained permissions to programmatically review and approve push protection bypass requests. This enables your organization to streamline security request reviews and enforce policies, or integrate with external security tools, ensuring that all reviews meet established standards. _For {% data variables.product.prodname_ghe_server %}, the use of {% data variables.product.prodname_github_apps %} to review bypass requests is available from version 3.19._ +> For more information about permissions, see [Organization permissions for "Organization bypass requests for secret scanning"](/enterprise-cloud@latest/rest/authentication/permissions-required-for-github-apps?apiVersion=2022-11-28#organization-permissions-for-organization-bypass-requests-for-secret-scanning). + When a contributor requests bypass privileges to push a commit containing a secret, this designated group of reviewers: * Receives an email notification containing a link to the request. diff --git a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/enabling-delegated-alert-dismissal-for-secret-scanning.md b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/enabling-delegated-alert-dismissal-for-secret-scanning.md index 4915169438c9..f973dc63f203 100644 --- a/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/enabling-delegated-alert-dismissal-for-secret-scanning.md +++ b/content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/enabling-delegated-alert-dismissal-for-secret-scanning.md @@ -37,6 +37,10 @@ You must configure delegated dismissal for your organization using a custom secu To learn more about security configurations, see [AUTOTITLE](/code-security/securing-your-organization/introduction-to-securing-your-organization-at-scale/about-enabling-security-features-at-scale). +>[!NOTE] +> You can use {% data variables.product.prodname_github_apps %} with fine-grained permissions to programmatically review and approve delegated dismissal requests. This enables your organization to streamline security request reviews and enforce policies, or integrate with external security tools, ensuring that all reviews meet established standards. _For {% data variables.product.prodname_ghe_server %}, the use of {% data variables.product.prodname_github_apps %} to review requests for delegated dismissals is available from version 3.19._ +> For more information about permissions, see [Organization permissions for "Organization bypass requests for secret scanning"](/enterprise-cloud@latest/rest/authentication/permissions-required-for-github-apps?apiVersion=2022-11-28#organization-permissions-for-organization-bypass-requests-for-secret-scanning). + {% ifversion secret-scanning-alert-dismiss-custom-role %} ## Configuring delegated dismissal for an enterprise From ed7c9d27b4c647ea9a255d594fe3f3777514f50b Mon Sep 17 00:00:00 2001 From: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Date: Wed, 6 Aug 2025 09:49:15 +0100 Subject: [PATCH 4/4] Premium request billing active on GHE.com (#56990) --- ...overview-for-github-enterprise-cloud-with-data-residency.md | 1 - content/copilot/concepts/billing/copilot-requests.md | 3 +-- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md b/content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md index 4ab10b875f72..82ebe792260c 100644 --- a/content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md +++ b/content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md @@ -28,7 +28,6 @@ The following features are currently unavailable on {% data variables.enterprise | {% data variables.product.prodname_copilot_short %} Metrics API | Currently unavailable | [AUTOTITLE](/rest/copilot/copilot-metrics) | | {% data variables.copilot.copilot_coding_agent %} | Currently unavailable | [AUTOTITLE](/copilot/concepts/about-copilot-coding-agent) | | Restricting {% data variables.product.prodname_actions %} policies to verified creators | Currently unavailable | [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allow-enterprise-and-select-non-enterprise-actions-and-reusable-workflows) | -| Billing for premium requests in {% data variables.product.prodname_copilot_short %} | Currently unavailable | [AUTOTITLE](/copilot/managing-copilot/understanding-and-managing-copilot-usage/understanding-and-managing-requests-in-copilot) | | {% data variables.product.prodname_github_models %} | Currently unavailable | [AUTOTITLE](/github-models/about-github-models) | | Some features currently in {% data variables.release-phases.public_preview %} or {% data variables.release-phases.private_preview %} | Certain features that are in a preview phase on {% data variables.product.prodname_dotcom_the_website %} may not be available on {% data variables.enterprise.data_residency_site %} | | diff --git a/content/copilot/concepts/billing/copilot-requests.md b/content/copilot/concepts/billing/copilot-requests.md index c2ffeabeb85f..7ce4b88f42c8 100644 --- a/content/copilot/concepts/billing/copilot-requests.md +++ b/content/copilot/concepts/billing/copilot-requests.md @@ -18,8 +18,7 @@ contentType: concepts --- > [!IMPORTANT] -> * Billing for premium requests began on June 18, 2025 for all paid {% data variables.product.prodname_copilot_short %} plans, and the request counters were only set to zero for paid plans. -> * {% data reusables.copilot.data-residency-availability %} +> * Billing for premium requests began on June 18, 2025, for all paid {% data variables.product.prodname_copilot_short %} plans on {% data variables.product.prodname_dotcom_the_website %}, and on August 1, 2025, on {% data variables.enterprise.data_residency_site %}. The request counters were only set to zero for paid plans. > * Premium request counters reset on the 1st of each month at 00:00:00 UTC. See [AUTOTITLE](/copilot/managing-copilot/understanding-and-managing-copilot-usage/monitoring-your-copilot-usage-and-entitlements). > * Certain requests may experience rate limits to accommodate high demand. Rate limits restrict the number of requests that can be made within a specific time period.