Merge pull request #24921 from github/repo-sync

repo sync

components/hooks/useWindowScroll.ts

@@ -1,24 +0,0 @@
-import { useState, useEffect } from 'react'
-
-// returns scroll position
-export function useWindowScroll(): number {
-  const [scrollPosition, setScrollPosition] = useState(
-    typeof window !== 'undefined' ? window.scrollY : 0
-  )
-
-  useEffect(() => {
-    const setScollPositionCallback = () => setScrollPosition(window.scrollY)
-
-    if (typeof window !== 'undefined') {
-      window.addEventListener('scroll', setScollPositionCallback)
-    }
-
-    return () => {
-      if (typeof window !== 'undefined') {
-        window.removeEventListener('scroll', setScollPositionCallback)
-      }
-    }
-  }, [])
-
-  return scrollPosition
-}

components/lib/getAnchorLink.ts

@@ -1 +0,0 @@
-export const getAnchorLink = (title: string) => title.toLowerCase().replace(/\s/g, '-')

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

@@ -16,7 +16,11 @@ topics:
 
 ## About teams
 
-You can use teams to organize, mention, and manage access for people in an organization. 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. 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.
+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.
+
+{% ifversion team-mentions-setting %}Organization owners and team maintainers can disable team notifications. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/configuring-team-notifications)."{% endif %}
+
+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.
 
 For more information, see:
 - "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"

content/organizations/organizing-members-into-teams/configuring-team-notifications.md

@@ -0,0 +1,27 @@
+---
+title: Configuring team notifications
+intro: 'Team maintainers and organization owners can configure notifications for specific teams.'
+versions:
+  feature: team-mentions-setting
+topics:
+  - Organizations
+  - Teams
+---
+
+Team maintainers and organization owners can enable or disable notifications for specific teams. When notifications are enabled, members of the team will receive notifications when the team is mentioned in an issue, pull request, or comment.
+
+Disabling team notifications won't unsubscribe people that are already subscribed to threads.
+
+{% note %}
+
+**Note:** This setting does not affect notifications for reviews requested from the team.
+
+{% endnote %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.teams %}
+1. In the list of teams, click the name of the team whose parent you'd like to change.
+{% data reusables.organizations.team_settings %}
+{% data reusables.organizations.team-notifications %}
+1. Click **Save changes**.

content/organizations/organizing-members-into-teams/creating-a-team.md

@@ -31,6 +31,7 @@ Only organization owners and maintainers of a parent team can create a new child
     * If your organization or enterprise account uses team synchronization, under "Identity Provider Groups", select the **Select Groups** dropdown menu, and click up to five identity provider groups to connect to the new team. For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
 {% endif %}
 {% data reusables.organizations.team_visibility %}
+{% data reusables.organizations.team-notifications %}
 {% data reusables.organizations.create_team %}
 1. Optionally, [give the team access to organization repositories](/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository).
 

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

@@ -29,6 +29,7 @@ children:
   - /managing-code-review-settings-for-your-team
   - /renaming-a-team
   - /changing-team-visibility
+  - /configuring-team-notifications
   - /synchronizing-a-team-with-an-identity-provider-group
   - /moving-a-team-in-your-organizations-hierarchy
   - /requesting-to-add-a-child-team
@@ -39,4 +40,3 @@ children:
   - /deleting-a-team
 shortTitle: Organize members into teams
 ---
-

data/features/team-mentions-setting.yml

@@ -0,0 +1,6 @@
+# Reference: #9959
+# Optionally disable notifications from team mentions
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.10'

data/reusables/organizations/team-notifications.md

@@ -0,0 +1,7 @@
+1.  Under "Team notifications", select **Enabled** or **Disabled**.
+
+    {% note %}
+
+    **Note:** This setting only applies to @mentions of the team name. This setting does not affect notifications for reviews requested from the team.
+
+    {% endnote %}