From 7796c67b5b936e420785cfbe8f7cdd3c748979a9 Mon Sep 17 00:00:00 2001 From: Camilla Moraes Date: Tue, 16 Jun 2026 14:21:37 -0700 Subject: [PATCH 1/3] Document concurrent PR limit for non-collaborators (#44711) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Stephanie Hong <41085564+JelloBagel@users.noreply.github.com> Co-authored-by: Sharra-writes --- ...imiting-interactions-in-your-repository.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index a0ace6073433..259557f65746 100644 --- a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -31,6 +31,25 @@ You can also enable activity limitations on all repositories owned by your perso 1. In the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Moderation options**, then click **Interaction limits**. {% data reusables.community.set-interaction-limit %} +## Limiting concurrent open pull requests for users without write access + +In a public repository, you can set a maximum number of pull requests that a user without write access can have open at the same time. When a user without write access reaches the limit, they can close or merge an existing pull request before they can open a new one. + +This setting helps maintainers manage contribution volume by preventing users from opening an excessive number of pull requests, which can overwhelm review queues and trigger unnecessary CI runs. The limit only applies to users without write access — users with write access or higher are not affected. + +### Adding trusted contributors to the bypass list + +Rather than granting full collaborator access, you can add trusted contributors to a bypass list, allowing them to exceed the pull request limit while keeping their permissions otherwise unchanged. This bypass is ideal for regular external contributors who routinely open multiple pull requests but do not need the additional permissions that come with collaborator access. + +You can manage the bypass list through either the UI or the API. The bypass list supports up to 100 users. + +### Configuring the pull request limit + +To configure the pull request limit, navigate to the **Interaction limits** settings page following the same steps described in [AUTOTITLE](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository), then: + +1. Under **Pull request limits**, select the maximum number of concurrent open pull requests allowed for users without write access. +1. Optionally, under **Bypass list**, search for and select the users you want to allow to bypass the pull request limit. + ## Further reading * [AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) From 8d1e44051dab65cefbfa254670f9b56ebc2ff80a Mon Sep 17 00:00:00 2001 From: Andy Sterland Date: Tue, 16 Jun 2026 14:55:40 -0700 Subject: [PATCH 2/3] Update Visual Studio versions and feature support (#61595) Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: andysterland <10997361+andysterland@users.noreply.github.com> Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com> --- data/tables/copilot/copilot-matrix.yml | 129 +++++-------------------- 1 file changed, 25 insertions(+), 104 deletions(-) diff --git a/data/tables/copilot/copilot-matrix.yml b/data/tables/copilot/copilot-matrix.yml index 9234053320bb..e4ca9ee2d5ff 100644 --- a/data/tables/copilot/copilot-matrix.yml +++ b/data/tables/copilot/copilot-matrix.yml @@ -443,143 +443,64 @@ ides: 0.0.0: not-supported Visual Studio: versions: - - 18.0.0 - - 17.14.13 - - 17.14.6 + - 18.6.0 - 17.14.0 - - 17.13.0 - - 0.0.0 versionGroups: latest releases: - - 18.0.0 - - 17.14.13 - - 17.14.6 - - 17.14.0 - - 17.13.0 - 2025 releases: - - 18.0.0 - - 17.14.13 - - 17.14.6 + - 18.6.0 - 17.14.0 - - 17.13.0 features: .NET Upgrade Agent: - 18.0.0: supported - 17.14.13: preview - 17.14.6: preview - 17.14.0: preview - 17.13.0: preview - 0.0.0: preview + 18.6.0: supported + 17.14.0: supported Agent skills: - 18.0.0: not-supported - 17.14.13: not-supported - 17.14.6: not-supported + 18.6.0: supported 17.14.0: not-supported - 17.13.0: not-supported - 0.0.0: not-supported Agent mode: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported - 17.14.0: preview - 17.13.0: not-supported - 0.0.0: not-supported + 18.6.0: supported + 17.14.0: supported BYOK: - 18.0.0: supported - 17.14.13: not-supported - 17.14.6: not-supported - 17.14.0: not-supported - 17.13.0: not-supported - 0.0.0: not-supported + 18.6.0: supported + 17.14.0: supported Chat: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: supported - 0.0.0: supported Checkpoints: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: not-supported Code completion: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: supported - 0.0.0: supported Code referencing: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: supported - 0.0.0: not-supported Copilot code review: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: supported - 0.0.0: supported Custom agents: - 18.0.0: preview - 17.14.13: not-supported - 17.14.6: not-supported + 18.6.0: supported 17.14.0: not-supported - 17.13.0: not-supported - 0.0.0: not-supported Custom instructions: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: supported - 0.0.0: supported Edit mode: - 18.0.0: closing-down - 17.14.6: supported - 17.14.0: supported - 17.13.0: supported - 0.0.0: not-supported + 18.6.0: not-supported + 17.14.0: not-supported MCP: - 18.0.0: supported - 17.14.13: supported - 17.14.6: preview - 17.14.0: preview - 17.13.0: not-supported - 0.0.0: not-supported + 18.6.0: supported + 17.14.0: supported Next edit suggestions: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: not-supported - 0.0.0: not-supported Prompt files: - 18.0.0: supported - 17.14.13: not-supported - 17.14.6: not-supported - 17.14.0: not-supported - 17.13.0: not-supported - 0.0.0: not-supported + 18.6.0: supported + 17.14.0: supported Vision: - 18.0.0: supported - 17.14.13: supported - 17.14.6: supported + 18.6.0: supported 17.14.0: supported - 17.13.0: preview - 0.0.0: preview Workspace indexing: - 18.0.0: supported - 17.14.13: not-supported - 17.14.6: not-supported + 18.6.0: supported 17.14.0: not-supported - 17.13.0: not-supported - 0.0.0: not-supported JetBrains: versions: - 1.5.66 From 17d4c612d14c6f60efb18c6d5df7a81d6a58d48a Mon Sep 17 00:00:00 2001 From: William Choe Date: Tue, 16 Jun 2026 16:20:45 -0600 Subject: [PATCH 3/3] Update setup user authentication instructions (#44708) Co-authored-by: Sharra-writes --- .../concepts/identity-and-access-management/setup-user.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/admin/concepts/identity-and-access-management/setup-user.md b/content/admin/concepts/identity-and-access-management/setup-user.md index 9d47ce1019a2..242f01a8edee 100644 --- a/content/admin/concepts/identity-and-access-management/setup-user.md +++ b/content/admin/concepts/identity-and-access-management/setup-user.md @@ -31,6 +31,13 @@ When you create the password, we strongly recommend that you **enable two-factor Unlike provisioned managed users, the setup user cannot sign in via SSO. +If you need to access enterprise recovery codes: +1. Navigate to github.com/login. +1. Enter the setup user's username (for example, shortcode_admin) and password. +1. Complete your 2FA challenge, or enter an enterprise recovery code if prompted. + +Enterprise recovery codes are not the same as personal two-factor authentication recovery codes. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-iam/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes). + - **Without 2FA enabled**, you must provide an enterprise recovery code **every** time you sign in. - If **2FA is enabled**, you must sign in with a successful 2FA challenge response. You only need to enter an enterprise recovery code to access enterprise settings.