Merge pull request #42579 from github/repo-sync

Repo sync

Author: docs-bot

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

@@ -54,11 +54,11 @@ Each team has its own page within an organization. On a team's page, you can vie
 
 ## Nested teams
 
-You can reflect your group or company's hierarchy within your {% data variables.product.github %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams.
+You can reflect your group or company's hierarchy within your {% data variables.product.github %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. Each nested team functions as a distinct entity with its own unique URL and directory within your organization.
 
 Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people.
 
-For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification.
+For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification. When mentioning a team, you do not need to include the full hierarchical path. Even though a team is nested, it retains a flat handle for mentions.
 
 To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team.
 

src/audit-logs/data/ghec/enterprise.json

@@ -1812,6 +1812,29 @@
       "created_at"
     ]
   },
+  {
+    "action": "business.invite_unaffiliated_member",
+    "description": "An invitation for someone to join an enterprise was sent.",
+    "docs_reference_links": "N/A",
+    "fields": [
+      "actor",
+      "actor_id",
+      "user_agent",
+      "request_id",
+      "request_access_security_header",
+      "name",
+      "invitation_id",
+      "email",
+      "business",
+      "business_id",
+      "action",
+      "_document_id",
+      "@timestamp",
+      "created_at",
+      "operation_type",
+      "actor_is_bot"
+    ]
+  },
   {
     "action": "business.members_can_update_protected_branches.clear",
     "description": "An enterprise owner unset a policy for whether members of an enterprise can update protected branches on repositories for individual organizations. Organization owners can choose whether to allow updating protected branches settings.",

src/audit-logs/lib/config.json

@@ -9,5 +9,5 @@
     "git": "Note: Git events have special access requirements and retention policies that differ from other audit log events. For GitHub Enterprise Cloud, access Git events via the REST API only with 7-day retention. For GitHub Enterprise Server, Git events must be enabled in audit log configuration and are not included in search results.",
     "sso_redirect": "Note: Automatically redirecting users to sign in is currently in beta for Enterprise Managed Users and subject to change."
   },
-  "sha": "6db8e8d59222d152b5a2df1030d78dee55aeba92"
+  "sha": "c64727fee495d421abf1a345efb7478fc7afc781"
 }