Repo sync

content/admin/monitoring-and-managing-your-instance/configuring-clustering/rebalancing-cluster-workloads.md

@@ -63,8 +63,7 @@ After you determine which jobs are unbalanced across your cluster's nodes, you c
 
 You can schedule rebalancing of jobs on your cluster by setting and applying configuration values for {% data variables.location.product_location %}.
 
-> [!NOTE]
-> Currently, you can only schedule reallocation of jobs for the HTTP server, `github-unicorn`.
+By default, scheduled rebalancing considers all eligible jobs, including `github-unicorn` and other eligible services. You can apply a job filter with `-j`.
 
 1. To configure automatic, hourly balancing of jobs, run the following command.
 

src/github-apps/lib/config.json

@@ -60,5 +60,5 @@
       "2022-11-28"
     ]
   },
-  "sha": "c66e298030d4070b70a569dcd4268b3a041b5380"
+  "sha": "320307e220815d528224ca891cf8a9e3c0243678"
 }

src/rest/data/fpt-2022-11-28/users.json

@@ -9,7 +9,7 @@
       "subcategory": "users",
       "parameters": [],
       "bodyParameters": [],
-      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>",
+      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {
@@ -5230,7 +5230,7 @@
         }
       ],
       "bodyParameters": [],
-      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>",
+      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {

src/rest/data/fpt-2026-03-10/users.json

@@ -9,7 +9,7 @@
       "subcategory": "users",
       "parameters": [],
       "bodyParameters": [],
-      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>",
+      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {
@@ -5192,7 +5192,7 @@
         }
       ],
       "bodyParameters": [],
-      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>",
+      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {

src/rest/data/ghec-2022-11-28/users.json

@@ -9,7 +9,7 @@
       "subcategory": "users",
       "parameters": [],
       "bodyParameters": [],
-      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>",
+      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {
@@ -5230,7 +5230,7 @@
         }
       ],
       "bodyParameters": [],
-      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>",
+      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {

src/rest/data/ghec-2026-03-10/users.json

@@ -9,7 +9,7 @@
       "subcategory": "users",
       "parameters": [],
       "bodyParameters": [],
-      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>",
+      "descriptionHTML": "<p>OAuth app tokens and personal access tokens (classic) need the <code>read:user</code> scope, or the broader <code>user</code> scope, for this endpoint to return the private user response. The private user response includes additional fields such as <code>private_gists</code>, <code>total_private_repos</code>, <code>owned_private_repos</code>, <code>disk_usage</code>, <code>collaborators</code>, and <code>two_factor_authentication</code>. Tokens without these scopes receive the public user response.</p>\n<p>The private and public user response types are unrelated to the <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/concepts/personal-profile#private-profiles\">private profile</a> setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as <code>followers</code> and <code>following</code>, may differ from an unauthenticated response.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {
@@ -5192,7 +5192,7 @@
         }
       ],
       "bodyParameters": [],
-      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>",
+      "descriptionHTML": "<p>Lists all of your email addresses, and specifies which one is visible\nto the public.</p>\n<p>OAuth app tokens and personal access tokens (classic) need the <code>user:email</code> scope to use this endpoint.</p>\n<p>For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format <code>email+shortcode@domain.com</code> instead of their actual email. This placeholder email <a href=\"https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification/\">may cause issues with some third-party apps</a>. Once the user has <a href=\"https://docs.github.com/enterprise-cloud@latest/account-and-profile/how-tos/email-preferences/verifying-your-email-address\">verified their email address</a>, the endpoint will return their real email.</p>",
       "codeExamples": [
         {
           "request": {