Skip to content

Commit 0a0c11d

Browse files
authored
Merge pull request #5739 from github/lee-dohm-old-fixes-new-branch
New companion to 5538
2 parents afcb44f + 303ba3d commit 0a0c11d

File tree

78 files changed

+121
-120
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

78 files changed

+121
-120
lines changed
9.36 KB
Loading
20.1 KB
Loading

content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ In your organization's repositories, blocked users also cannot:
5757
1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
5858

5959
{% data reusables.profile.access_org %}
60-
{% data reusables.organizations.org_settings %}
60+
{% data reusables.profile.org_settings %}
6161
{% data reusables.organizations.block_users %}
6262
6. Under "Block a user", type the username of the user you'd like to block.
6363
![Username field](/assets/images/help/organizations/org-block-username-field.png)

content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ If you selected a specific amount of time to block the user, they will be automa
3131

3232

3333
{% data reusables.profile.access_org %}
34-
{% data reusables.organizations.org_settings %}
34+
{% data reusables.profile.org_settings %}
3535
{% data reusables.organizations.block_users %}
3636
5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**.
3737
![Unblock user button](/assets/images/help/organizations/org-unblock-user-button.png)

content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ topics:
1212

1313

1414
{% data reusables.profile.access_org %}
15-
{% data reusables.organizations.org_settings %}
15+
{% data reusables.profile.org_settings %}
1616
{% data reusables.organizations.block_users %}
1717
5. Under "Blocked users", review the list of users who are blocked from your organization.
1818
![List of blocked users](/assets/images/help/settings/list-of-blocked-users-for-org.png)

content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,13 @@ Members of the organization are not affected by any of the limit types.
2424

2525
When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
2626

27-
Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
27+
Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
2828

2929
### Limiting interactions in your organization
3030

3131

3232
{% data reusables.profile.access_org %}
33-
{% data reusables.organizations.org_settings %}
33+
{% data reusables.profile.org_settings %}
3434
1. In the organization settings sidebar, click **Moderation settings**.
3535
!["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png)
3636
1. Under "Moderation settings", click **Interaction limits**.

content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,16 +13,16 @@ Once your organization has been verified, you can publish paid plans for your ap
1313

1414
To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)."
1515

16-
### Requesting publisher verification
16+
### Requesting publisher verification
1717

1818

1919
{% data reusables.profile.access_org %}
20-
{% data reusables.organizations.org_settings %}
20+
{% data reusables.profile.org_settings %}
2121
1. In the left sidebar, click **Developer settings**.
2222
![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png)
2323
1. Under "Developer settings", click **Publisher Verification**.
2424
![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png)
25-
1. Under "Publisher Verification", complete the information in the checklist:
25+
1. Under "Publisher Verification", complete the information in the checklist:
2626
- Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
2727
- Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."
2828
- Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."

content/github/administering-a-repository/restoring-a-deleted-repository.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Restoring a repository will not restore release attachments or team permissions.
3333

3434

3535
{% data reusables.profile.access_org %}
36-
{% data reusables.organizations.org_settings %}
36+
{% data reusables.profile.org_settings %}
3737
{% data reusables.organizations.deleted-repos %}
3838
{% data reusables.user_settings.restore-repo %}
3939
{% data reusables.user_settings.restore-confirmation %}

content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ When you enable access and security for a repository owned by your organization,
3939

4040

4141
{% data reusables.profile.access_org %}
42-
{% data reusables.organizations.org_settings %}
42+
{% data reusables.profile.org_settings %}
4343
{% data reusables.organizations.click-codespaces %}
44-
5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces.
44+
5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces.
4545
![Radio button for "Selected users"](/assets/images/help/organizations/select-selected-users-radio-button.png)
4646
1. Under "Access and security", select the setting you want for your organization.
4747
![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)

content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Downgrading to {% data variables.product.prodname_free_team %} for organizations
5858

5959

6060
{% data reusables.profile.access_org %}
61-
{% data reusables.organizations.org_settings %}
61+
{% data reusables.profile.org_settings %}
6262
{% data reusables.organizations.billing_plans %}
6363
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
6464
![Buy Enterprise and Downgrade to Team buttons](/assets/images/help/organizations/finish-trial-buttons.png)

0 commit comments

Comments
 (0)