Repo sync

content/admin/managing-iam/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md

@@ -25,7 +25,13 @@ redirect_from:
 
 When you configure SAML SSO at the organization level, each organization must be configured with a unique SSO tenant in your IdP, which means that your members will be associated with a unique SAML identity record for each organization they have successfully authenticated with. If you configure SAML SSO for your enterprise account instead, each enterprise member will have one SAML identity that is used for all organizations owned by the enterprise account.
 
-After you configure SAML SSO for your enterprise account, the new configuration will override any existing SAML SSO configurations for organizations owned by the enterprise account. Any team synchronization settings you have configured will also be removed from these organizations. If you intend to re-enable team synchronization, before enabling SAML SSO for your enterprise, take note of the current team sync configuration in the affected organizations. For more information, see "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
+After you configure SAML SSO for your enterprise account, the new configuration will override any existing SAML SSO configurations for organizations owned by the enterprise account. Any team synchronization settings you have configured will also be removed from these organizations.
+
+* Your organization members will be removed from {% data variables.product.prodname_dotcom %} teams following the removal of the organization's team synchronization settings.
+* If you intend to re-enable team synchronization, before enabling SAML SSO for your enterprise, take note of the current team sync configuration in the affected organizations. See "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
+
+  You will need to re-add your organization members to {% data variables.product.prodname_dotcom %} teams after re-enabling team synchronization.
+* Schedule a time to make changes to your organization's team synchronization settings when people aren't actively using your organization's resources. Changes to team synchronization may result in some downtime for your members.
 
 Enterprise members will not be notified when an enterprise owner enables SAML for the enterprise account. If SAML SSO was previously enforced at the organization level, members should not see a major difference when navigating directly to organization resources. The members will continue to be prompted to authenticate via SAML. If members navigate to organization resources via their IdP dashboard, they will need to click the new tile for the enterprise-level app, instead of the old tile for the organization-level app. The members will then be able to choose the organization to navigate to.
 

content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud.md

@@ -19,6 +19,9 @@ We currently only support migrating the following repository data from Bitbucket
 * Git source (including commit history)
 * Pull requests (including comments, pull request reviews, pull request review comments at the file and line level, required reviewers, and attachments)
 
+  > [!NOTE]
+  > Users may receive a `500` error when attempting to view a pull request, if the pull request was merged and the head branch deleted on Bitbucket Server prior to migration. Bitbucket Server removes specific Git references to objects for such pull requests, and consequently those Git objects associated with the pull request are unable to be migrated.
+
 ## Data that is not migrated
 
 Currently, the following data is **not** migrated.

content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md

@@ -31,3 +31,19 @@ Your {% data variables.product.prodname_sponsors %} profile tells potential spon
 {% data reusables.sponsors.edit-featured-work %}
 {% data reusables.sponsors.opt-in-to-being-featured %}
 {% data reusables.sponsors.save-profile %}
+
+## Selecting Featured Sponsors
+
+Featured sponsors allows you to spotlight your sponsors. You can opt to automatically display your top 10 sponsors, manually select 10 sponsors, or feature no sponsors.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+1. Under "Featured Sponsors", select the checkbox for the option to display your featured sponsors automatically or manually.
+
+    * If opting to automatically feature your top 10 sponsors, select the dial button and click **Update profile**.
+
+    * To manually add sponsors, select the **Manually add my featured sponsors** option and click **Add or remove**.
+
+    * A pop up window will display allowing you to search your sponsors. Click on the desired sponsors and click **Save**.
+
+{% data reusables.sponsors.save-profile %}

data/reusables/sponsors/navigate-to-sponsors-dashboard.md

@@ -1,12 +1,2 @@
 1. In the upper-right corner of any page, click your profile photo, then click **Your sponsors**.
-
-{% ifversion global-nav-update %}
-
-  ![Screenshot of the profile options dropdown menu. One option, labeled "Your sponsors," is outlined in dark orange.](/assets/images/help/sponsors/access-sponsors-dashboard-global-nav-update.png)
-
-{% else %}
-
-  ![Screenshot of the profile options dropdown menu. One option, labeled "Your sponsors," is outlined in dark orange.](/assets/images/help/sponsors/access-github-sponsors-dashboard.png)
-
-{% endif %}
 1. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**.