Repo sync

.github/workflows/create-changelog-pr.yml

@@ -122,7 +122,7 @@ jobs:
             core.setOutput('pull-request-number', pullRequest.number);
             core.setOutput('pull-request-url', pullRequest.html_url);
 
-      - name: Add 'ready-for-doc-review' label to PR
+      - name: Add 'ready-for-doc-review' and 'skip FR board' labels to PR
         if: env.CONTINUE_WORKFLOW == 'true'
         uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd
         env:
@@ -135,7 +135,7 @@ jobs:
               owner: context.repo.owner,
               repo: context.repo.repo,
               issue_number: Number(process.env.PULL_REQUEST_NUMBER),
-              labels: ['ready-for-doc-review']
+              labels: ['ready-for-doc-review','skip FR board']
             });
 
       - name: Assign PR to commenter

content/admin/managing-iam/provisioning-user-accounts-with-scim/managing-team-memberships-with-identity-provider-groups.md

@@ -57,7 +57,7 @@ If you use Microsoft Entra ID (previously known as Azure AD) as your IdP, you ca
 
 Enterprise owners can create teams at the enterprise level. {% data reusables.copilot.direct-assignment-rollout %}
 
-For instructions on creating an enterprise team and syncing it with an IdP group, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/create-enterprise-teams).
+Most of the instructions in this article apply to organization-level teams. For instructions on creating an enterprise team and syncing it with an IdP group, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/create-enterprise-teams).
 
 {% endif %}
 

content/admin/overview/about-teams.md

@@ -0,0 +1,56 @@
+---
+title: About teams in an enterprise
+intro: 'Learn how teams simplify administration of user access, licensing, and communication.'
+versions:
+  ghec: '*'
+shortTitle: About teams
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+---
+
+## What are teams?
+
+Teams are **groups of users** in an enterprise or organization. By creating teams, you can manage users at scale and simplify access, licensing, and communication. For example, you could create an auditor team for users who need access to audit logs, or a {% data variables.product.prodname_copilot_short %} team for users who receive {% data variables.product.prodname_copilot_short %} licenses.
+
+Administrators can create teams in an enterprise account or in organizations within an enterprise.
+
+* **Enterprise teams** are managed by enterprise owners and can include users from across the enterprise and its organizations. Currently, enterprise teams are used to manage {% data variables.product.prodname_copilot %} licenses for directly assigned users. {% data variables.product.company_short %} plans to expand the capabilities in the near future to include organization and role assignment.
+* **Organization teams** are managed by organization administrators and can only include members of a single organization. Organization administrators can grant teams access to organization repositories, and organization members can mention teams in issues and discussions or add them as reviewers on pull requests.
+
+## Can I manage teams from an identity provider?
+
+If you have integrated {% data variables.product.github %} with an identity provider (IdP), you can link teams on {% data variables.product.github %} with groups in your IdP. When membership of the IdP group changes, the change is reflected in the {% data variables.product.github %} team, allowing you to centralize access management.
+
+The capabilities of this feature depend on whether you use {% data variables.product.prodname_emus %} or personal accounts.
+
+### {% data variables.product.prodname_emus %}
+
+You can make changes to IdP groups to manage repository access, add or remove users from organizations, or grant or remove {% data variables.product.prodname_copilot %} licenses. For example, if a new user is added to an IdP group that is linked to a team with access to an organization, the user receives access to that organization. For more information, see [AUTOTITLE](/admin/managing-iam/provisioning-user-accounts-with-scim/managing-team-memberships-with-identity-provider-groups#about-team-management-with-enterprise-managed-users).
+
+This feature is available with both enterprise and organization teams.
+
+### Personal accounts
+
+Team synchronization allows you to centrally manage any privileges linked to an organization team, such as repository access and CODEOWNER status. However, team sync cannot be used to add users to organizations where they don't already have access. For more information, see [AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise).
+
+Team sync with personal accounts is only available with organization teams, and you must use Entra ID or Okta as an IdP.
+
+## What kind of team should I use?
+
+To simplify administration at scale, {% data variables.product.company_short %} recommends using enterprise teams wherever possible. However, you may need to create organization teams if the functionality you need is not covered by enterprise teams. {% data variables.product.company_short %} plans to address some of these limitations in the near future.
+
+Unlike organization teams, enterprise teams currently do **not** support:
+
+* Repository or organization access
+* `@-mentions` of the team name in organizations
+* Team sync if you use {% data variables.product.prodname_ghe_cloud %} with personal accounts
+* CODEOWNER status
+* Secret teams
+* Nested teams
+* Team maintainers
+
+In addition, enterprise teams are currently limited to 50 teams for a single enterprise and 500 users to each team.
+
+For more information about the capabilities of organization teams, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams).

content/admin/overview/index.md

@@ -19,6 +19,7 @@ children:
   - /best-practices-for-enterprises
   - /establishing-a-governance-framework-for-your-enterprise
   - /accessing-compliance-reports-for-your-enterprise
+  - /about-teams
 ---
 
 For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).

content/organizations/organizing-members-into-teams/about-teams.md

@@ -18,9 +18,13 @@ allowTitleToDifferFromFilename: true
 
 You can use teams to manage access for people in an organization, and for sending notifications. Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Teams can only be made up of members of your organization, outside collaborators are unable to be on a team.
 
-Organization owners and team maintainers can disable team notifications. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/configuring-team-notifications).
+{% ifversion not ghes %}
 
-Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
+>![TIP] If you use an enterprise account, you can also create teams at the enterprise level. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-teams).
+
+{% endif %}
+
+Organization members can send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
 
 For more information, see:
 * [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository)

content/site-policy/github-terms/github-terms-of-service.md

@@ -146,6 +146,12 @@ You retain all moral rights to Your Content that you upload, publish, or submit
 
 To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
 
+### 8. Access Reciprocity
+
+By using automated means to access, collect, or otherwise use (“Access”) any publicly accessible Content from the Service for the purpose of developing or training any commercially available artificial intelligence model, machine learning system, or similar technology (a "Commercial AI System"), you hereby waive any and all policies, terms, conditions, or contractual provisions governing products, services, websites or datasets you own or operate that would otherwise prohibit, restrict, or place conditions upon GitHub's Access to any publicly accessible data, information or content associated with your products or services, including for the purpose of developing or training any Commercial AI System. You further agree not to impose technical or other targeted measures to restrict or retaliate against such Access.
+
+This Section D.8 does not apply to Access solely for the purpose of academic research or if, on the date you Access the Content, the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month. For the purposes of this Section, "you" shall refer to you and any entity that directly or indirectly controls, is controlled by, or is under common control with you (affiliates). 
+
 ## E. Private Repositories
 
 **Short version:** _We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent._
@@ -351,7 +357,7 @@ We reserve the right at any time and from time to time to modify or discontinue,
 
 ### 1. Governing Law
 
-Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California.
+Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California. However, any claim for injunctive relief with respect to a violation of section D.8 may be brought in any jurisdiction.
 
 ### 2. Non-Assignability