jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Fix alerts to match the markdown notation (#35444)

Browse Source 
Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com>
This commit is contained in:
Artur Kordowski
2024-11-27 17:16:24 +01:00
committed by GitHub
parent 27a19de50c
commit e4c74eb99e
5 changed files with 19 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
content/admin/managing-iam/using-ldap-for-enterprise-iam/using-ldap.md
View File

@@ -158,20 +158,15 @@ A synchronization job will also run at the specified time interval to perform th
{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
{% warning %} > [!WARNING]
> When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to.
**Security Warning:** >
> This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including:
When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to. >
> * The existence of specific LDAP Groups visible to the _Domain search user_.
This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including: > * Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group.
>
* The existence of specific LDAP Groups visible to the _Domain search user_. > If disclosing such information is not desired, your company or organization should restrict the permissions of the configured _Domain search user_ in the admin console. If such restriction isn't possible, contact us by visiting {% data variables.contact.contact_ent_support %}.
* Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group.
If disclosing such information is not desired, your company or organization should restrict the permissions of the configured _Domain search user_ in the admin console. If such restriction isn't possible, contact us by visiting {% data variables.contact.contact_ent_support %}.
{% endwarning %}
## Supported LDAP group object classes ## Supported LDAP group object classes

7
content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
View File

@@ -314,11 +314,8 @@ This SARIF output file has example values to show the minimum required propertie
This SARIF output file has example of values for the field `originalUriBaseIds`, showing the minimum required properties a SARIF producer should include when using relative URI references. This SARIF output file has example of values for the field `originalUriBaseIds`, showing the minimum required properties a SARIF producer should include when using relative URI references.
{% note %} > [!NOTE]
> While this property is not required by {% data variables.product.prodname_dotcom %} for the {% data variables.product.prodname_code_scanning %} results to be displayed correctly, it is required to produce a valid SARIF output when using relative URI references.
**Note:** While this property is not required by {% data variables.product.prodname_dotcom %} for the {% data variables.product.prodname_code_scanning %} results to be displayed correctly, it is required to produce a valid SARIF output when using relative URI references.
{% endnote %}
```json ```json
{ {

11
content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
View File

@@ -73,13 +73,10 @@ Because many {% data variables.product.prodname_ghe_server %} instances sit behi
You must first set up blob storage with a supported cloud provider, then configure your settings in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}. You must first set up blob storage with a supported cloud provider, then configure your settings in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}.
{% note %} > [!NOTE]
> You only need to configure blob storage if you use {% data variables.product.prodname_ghe_server %} versions 3.8 or higher. If you use {% data variables.product.prodname_ghe_server %} versions 3.7 or lower, skip to "[Step 4: Set up a migration source in {% data variables.product.prodname_ghe_cloud %}](#step-4-set-up-a-migration-source-in-github-enterprise-cloud)."
**Note**: You only need to configure blob storage if you use {% data variables.product.prodname_ghe_server %} versions 3.8 or higher. If you use {% data variables.product.prodname_ghe_server %} versions 3.7 or lower, skip to "[Step 4: Set up a migration source in {% data variables.product.prodname_ghe_cloud %}](#step-4-set-up-a-migration-source-in-github-enterprise-cloud)." >
> Blob storage is required to migrate repositories with large Git source or metadata. If you use {% data variables.product.prodname_ghe_server %} versions 3.7 or lower, you will not be able to perform migrations where your Git source or metadata exports exceed 2GB. To perform these migrations, update to {% data variables.product.prodname_ghe_server %} versions 3.8 or higher.
Blob storage is required to migrate repositories with large Git source or metadata. If you use {% data variables.product.prodname_ghe_server %} versions 3.7 or lower, you will not be able to perform migrations where your Git source or metadata exports exceed 2GB. To perform these migrations, update to {% data variables.product.prodname_ghe_server %} versions 3.8 or higher.
{% endnote %}
### Setting up blob storage with a supported cloud provider ### Setting up blob storage with a supported cloud provider

7
content/organizations/managing-organization-settings/deleting-an-organization-account.md
View File

@@ -25,11 +25,8 @@ shortTitle: Delete organization
{% endif %} {% endif %}
Deleting your organization account removes all repositories, forks of private repositories, wikis, issues, pull requests, and project or organization pages. {% ifversion fpt or ghec %}Your billing will end and, after 90 days, the organization name becomes available for use on a new user or organization account. Deleting your organization account removes all repositories, forks of private repositories, wikis, issues, pull requests, and project or organization pages. {% ifversion fpt or ghec %}Your billing will end and, after 90 days, the organization name becomes available for use on a new user or organization account.
{% tip %} > [!TIP]
> If you rename an organization, you can create a new organization with the same name immediately. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/renaming-an-organization)."
**Tip**: If you rename an organization, you can create a new organization with the same name immediately. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/renaming-an-organization)."
{% endtip %}
{% endif %} {% endif %}

7
data/reusables/secret-scanning/beta-prs-discussions-wikis-scanned.md
View File

@@ -1,11 +1,8 @@
{% ifversion ghes < 3.15 %} {% ifversion ghes < 3.15 %}
{% ifversion secret-scanning-enhancements-prs-discussions %} {% ifversion secret-scanning-enhancements-prs-discussions %}
{% note %} > [!NOTE]
> The scanning of content in pull requests and {% data variables.product.prodname_discussions %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
**Note:** The scanning of content in pull requests and {% data variables.product.prodname_discussions %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
{% endnote %}
{% endif %} {% endif %}
{% endif %} {% endif %}