Skip to content

Commit af0d57c

Browse files
authored
Merge pull request #31960 from github/repo-sync
Repo sync
2 parents bf49a28 + 082b64b commit af0d57c

21 files changed

Lines changed: 31 additions & 80 deletions

File tree

content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ You can add default community health files to a public repository called `.githu
2525
- The `.github` folder
2626
- The `docs` folder
2727

28-
For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a _config.yml_ file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
28+
For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder, including issue templates or a _config.yml_ file, none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
2929

3030
Default files won’t appear in the file browser or Git history and are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
3131

@@ -37,7 +37,7 @@ As a repository maintainer, you can use the community standards checklist to see
3737

3838
## Supported file types
3939

40-
You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
40+
You can create defaults in your organization or personal account for the following community health files:
4141

4242
Community health file | Description
4343
--- | ---{% ifversion fpt or ghec %}
@@ -46,20 +46,20 @@ _CONTRIBUTING.md_ | A CONTRIBUTING file communicates how people should contribut
4646
Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[AUTOTITLE](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
4747
_FUNDING.yml_ | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)."{% endif %}
4848
_GOVERNANCE.md_ | A GOVERNANCE file lets people know about how your project is governed. For example, it might discuss project roles and how decisions are made.
49-
Issue and pull request templates{% ifversion fpt or ghes or ghec %} and _config.yml_{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."{% ifversion fpt or ghes or ghec %}
50-
`SECURITY.md` | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
49+
Issue and pull request templates and _config.yml_ | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
50+
`SECURITY.md` | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[AUTOTITLE](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
5151
_SUPPORT.md_ | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project)."
5252

5353
You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
5454

5555
## Creating a repository for default files
5656

5757
{% data reusables.repositories.create_new %}
58-
1. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
58+
1. Use the **Owner** drop-down menu, and select the organization or personal account you want to create default files for.
5959
![Screenshot of the owner menu for a new {% data variables.product.prodname_dotcom %} repository. The menu shows two options, octocat and github.](/assets/images/help/repository/create-repository-owner.png)
6060
1. In the "Repository name" field, type **.github**.
6161
1. Optionally, in the "Description" field, type a description.
6262
1. Make sure the repository status is set to **Public**. A repository for default files cannot be private.
6363
{% data reusables.repositories.initialize-with-readme %}
6464
{% data reusables.repositories.create-repo %}
65-
1. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
65+
1. In the repository, create one of the supported community health files. Issue templates and their configuration file must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."

content/get-started/accessibility/keyboard-shortcuts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,8 @@ The following sections list some of the available keyboard shortcuts, organized
4141
|-----------|------------
4242
|<kbd>G</kbd> <kbd>C</kbd> | Go to the **Code** tab
4343
|<kbd>G</kbd> <kbd>I</kbd> | Go to the **Issues** tab. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues)."
44-
|<kbd>G</kbd> <kbd>P</kbd> | Go to the **Pull requests** tab. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
45-
|<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[AUTOTITLE](/actions/learn-github-actions)."{% endif %}
44+
|<kbd>G</kbd> <kbd>P</kbd> | Go to the **Pull requests** tab. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
45+
|<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[AUTOTITLE](/actions/learn-github-actions)."
4646
|<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see "[AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
4747
|<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see "[AUTOTITLE](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion discussions %}
4848
|<kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}

content/get-started/onboarding/getting-started-with-your-github-account.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,13 +48,11 @@ To ensure you can use all the features in your {% data variables.product.product
4848
The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance.
4949
{% endif %}
5050

51-
{% ifversion fpt or ghes or ghec %}
52-
5351
### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
5452

5553
Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
5654

57-
{% ifversion passkeys %}Optionally, after you have configured 2FA, add a passkey to your account to enable a secure, passwordless login. For more information, see "[AUTOTITLE](/authentication/authenticating-with-a-passkey/about-passkeys)" and "[AUTOTITLE](/authentication/authenticating-with-a-passkey/managing-your-passkeys)."{% endif %}{% endif %}
55+
{% ifversion passkeys %}Optionally, after you have configured 2FA, add a passkey to your account to enable a secure, passwordless login. For more information, see "[AUTOTITLE](/authentication/authenticating-with-a-passkey/about-passkeys)" and "[AUTOTITLE](/authentication/authenticating-with-a-passkey/managing-your-passkeys)."{% endif %}
5856

5957
### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
6058

content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,12 +37,8 @@ You'll receive a notification when:
3737
- Someone mentions you in a gist.
3838
- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
3939

40-
{% ifversion fpt or ghes or ghec %}
41-
4240
You can pin gists to your profile so other people can see them easily. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile)."
4341

44-
{% endif %}
45-
4642
You can discover public gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. {% ifversion ghes %}Gist search uses the same search syntax as [code search](/search-github/searching-on-github/searching-code).{% endif %}
4743

4844
Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see "[AUTOTITLE](/get-started/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists)."

content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ To transfer an open issue to another repository, you must have write access to t
1818

1919
{% note %}
2020

21-
**Note**: You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}A private repository issue cannot be transferred to a public repository.{% endif %}
21+
**Note**: You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred to a public repository.
2222

2323
{% endnote %}
2424

content/issues/using-labels-and-milestones-to-track-work/managing-labels.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,8 @@ You can manage your work on {% data variables.product.product_name %} by creatin
4040

4141
Label | Description
4242
--- | ---
43-
`bug` | Indicates an unexpected problem or unintended behavior{% ifversion fpt or ghes or ghec %}
44-
`documentation` | Indicates a need for improvements or additions to documentation{% endif %}
43+
`bug` | Indicates an unexpected problem or unintended behavior
44+
`documentation` | Indicates a need for improvements or additions to documentation
4545
`duplicate` | Indicates similar {% ifversion fpt or ghec %}issues, pull requests, or discussions{% else %}issues or pull requests{% endif %}
4646
`enhancement` | Indicates new feature requests
4747
`good first issue` | Indicates a good issue for first-time contributors
@@ -54,9 +54,7 @@ Default labels are included in every new repository when the repository is creat
5454

5555
Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
5656

57-
{% ifversion fpt or ghes or ghec %}
5857
Organization owners can customize the default labels for repositories in their organization. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization)."
59-
{% endif %}
6058

6159
## Creating a label
6260

@@ -104,7 +102,7 @@ Deleting a label will remove the label from issues and pull requests.
104102

105103
## Further reading
106104

107-
- "[AUTOTITLE](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes or ghec %}
108-
- "[AUTOTITLE](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt or ghec %}
105+
- "[AUTOTITLE](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"
106+
- "[AUTOTITLE](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization)"{% ifversion fpt or ghec %}
109107
- "[AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %}
110108
- "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#using-emoji)"

content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,8 @@ For instance, the organization news feed shows updates when someone in the organ
4040
- Submits a pull request review comment.
4141
- Forks a repository.
4242
- Creates a wiki page.
43-
- Pushes commits.{% ifversion fpt or ghes or ghec %}
44-
- Creates a public repository.{% endif %}
43+
- Pushes commits.
44+
- Creates a public repository.
4545

4646
## Further information
4747

content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -55,17 +55,17 @@ To search for specific events, use the `action` qualifier in your query. Actions
5555
| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
5656
| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization.{% endif %}
5757
| `discussion_post` | Contains all activities related to discussions posted to a team page.
58-
| `discussion_post_reply` | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
59-
| `enterprise` | Contains activities related to enterprise settings. |{% endif %}
58+
| `discussion_post_reply` | Contains all activities related to replies to discussions posted to a team page.
59+
| `enterprise` | Contains activities related to enterprise settings. |
6060
| `hook` | Contains all activities related to webhooks.
6161
| `integration_installation` | Contains activities related to integrations installed in an account. |
6262
| `integration_installation_request` | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec %}
6363
| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization.
6464
| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.{% endif %}
6565
| `issue` | Contains activities related to deleting an issue. {% ifversion fpt or ghec %}
6666
| `marketplace_agreement_signature` | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
67-
| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes or ghec %}
68-
| `members_can_create_pages` | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %}
67+
| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
68+
| `members_can_create_pages` | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |
6969
| `org` | Contains activities related to organization membership.{% ifversion ghec %}
7070
| `org_credential_authorization` | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion secret-scanning-validity-check-audit-log %}
7171
| `org_secret_scanning_automatic_validity_checks` | Contains organization-level activities related to enabling and disabling automatic validity checks for {% data variables.product.prodname_secret_scanning %}. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#allowing-validity-checks-for-partner-patterns-in-an-organization)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}

content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -146,8 +146,6 @@ Note the following restrictions and behaviors for the target repositories:
146146

147147
{% endif %}
148148

149-
{% ifversion fpt or ghes or ghec %}
150-
151149
## Enabling workflows for private repository forks
152150

153151
{% data reusables.actions.private-repository-forks-overview %}
@@ -162,7 +160,6 @@ Note the following restrictions and behaviors for the target repositories:
162160
{% data reusables.profile.org_settings %}
163161
{% data reusables.organizations.settings-sidebar-actions-general %}
164162
{% data reusables.actions.private-repository-forks-configure %}
165-
{% endif %}
166163

167164
## Setting the permissions of the `GITHUB_TOKEN` for your organization
168165

content/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,13 +53,11 @@ In addition to managing organization-level settings, organization owners have ad
5353
Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
5454
{% endif %}
5555

56-
{% ifversion fpt or ghes or ghec %}
5756
{% note %}
5857

5958
**Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below.
6059

6160
{% endnote %}
62-
{% endif %}
6361

6462
{% rowheaders %}
6563

0 commit comments

Comments
 (0)