From 19498f1523086c92f27d69c67d61e8b003a4e462 Mon Sep 17 00:00:00 2001 From: Devin McInnis <1831398+devinmcinnis@users.noreply.github.com> Date: Sun, 19 Oct 2025 23:29:59 -0700 Subject: [PATCH 1/2] Update max assignee limit from 1 to 10 (#58046) Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../assigning-issues-and-pull-requests-to-other-github-users.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/content/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users.md index 0cca585caf36..ecad239992fa 100644 --- a/content/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/content/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -27,7 +27,7 @@ You may also be able to assign {% data variables.product.prodname_copilot_short {% endif %} -Issues and pull requests in public repositories, and in private repositories for a paid account, can have up to 10 people assigned. Private repositories on the free plan are limited to one person per issue or pull request. +Both issues and pull requests support up to 10 assignees. ## Assigning an individual issue or pull request From 8aa9b61ea16ba7f7c26211eafe419d571f46aa2a Mon Sep 17 00:00:00 2001 From: Prashanth Kannan Date: Mon, 20 Oct 2025 03:17:19 -0400 Subject: [PATCH 2/2] Add commit authors to list of users with perms for resolving secret scanning alerts (#58042) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../managing-alerts-from-secret-scanning/resolving-alerts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/resolving-alerts.md b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/resolving-alerts.md index 5dff57de2778..4ff4dfe4d407 100644 --- a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/resolving-alerts.md +++ b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning/resolving-alerts.md @@ -1,7 +1,7 @@ --- title: Resolving alerts from secret scanning intro: 'After reviewing the details of a secret scanning alert, you should fix and then close the alert.' -permissions: '{% data reusables.permissions.secret-scanning-alerts %}' +permissions: 'Repository owners, organization owners, security managers, commit authors, and users with the **admin** role' versions: fpt: '*' ghes: '*'