From e91b4f51df0c7d8154bc55dcb79bb48eb4659865 Mon Sep 17 00:00:00 2001 From: Anne-Marie <102995847+am-stead@users.noreply.github.com> Date: Tue, 21 Jan 2025 09:22:58 +0000 Subject: [PATCH 1/5] Hack Week 2025: update product.product_name in various folders (#54019) --- .../documenting-your-project-with-wikis/about-wikis.md | 4 ++-- .../adding-or-editing-wiki-pages.md | 4 ++-- .../editing-wiki-content.md | 2 +- .../adding-a-code-of-conduct-to-your-project.md | 2 +- .../creating-a-default-community-health-file.md | 4 ++-- .../configuring-issue-templates-for-your-repository.md | 2 +- .../about-github-copilot-free.md | 2 +- .../about-discussions.md | 2 +- ...collaborating-with-maintainers-using-discussions.md | 2 +- .../participating-in-a-discussion.md | 4 ++-- content/discussions/guides/finding-your-discussions.md | 4 ++-- .../managing-discussions-for-your-community/index.md | 2 +- .../managing-categories-for-discussions.md | 2 +- .../contribute-with-github-community-exchange/index.md | 2 +- .../apply-to-github-education-as-a-teacher.md | 2 +- content/education/guides.md | 6 +++--- .../manage-coursework-with-github-classroom/index.md | 2 +- ...bout-using-makecode-arcade-with-github-classroom.md | 4 ++-- .../create-a-group-assignment.md | 6 +++--- .../create-an-assignment-from-a-template-repository.md | 2 +- .../create-an-individual-assignment.md | 4 ++-- .../teach-with-github-classroom/manage-classrooms.md | 10 +++++----- .../use-the-git-and-github-starter-assignment.md | 4 ++-- .../using-github-classroom-with-github-cli.md | 2 +- content/education/quickstart.md | 10 +++++----- 25 files changed, 45 insertions(+), 45 deletions(-) diff --git a/content/communities/documenting-your-project-with-wikis/about-wikis.md b/content/communities/documenting-your-project-with-wikis/about-wikis.md index 6a980b828af1..8d8f419d1014 100644 --- a/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -14,7 +14,7 @@ topics: - Community --- -Every repository on {% data variables.product.product_name %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes). +Every repository on {% data variables.product.github %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes). With wikis, you can write content just like everywhere else on {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github). We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. @@ -22,7 +22,7 @@ With wikis, you can write content just like everywhere else on {% data variables If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.location.product_location %}{% else %}the public{% endif %}. If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only people with access to the repository can access the wiki. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility). -You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.location.product_location %} to contribute to a wiki in a public repository. For more information, see [AUTOTITLE](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis). +You can edit wikis directly on {% data variables.product.github %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.location.product_location %} to contribute to a wiki in a public repository. For more information, see [AUTOTITLE](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis). {% ifversion fpt or ghec %} diff --git a/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md index 36b327c9d4ef..ee005c8bfdac 100644 --- a/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md +++ b/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md @@ -1,6 +1,6 @@ --- title: Adding or editing wiki pages -intro: 'You can add and edit wiki pages directly on {% data variables.product.product_name %} or locally using the command line.' +intro: 'You can add and edit wiki pages directly on {% data variables.product.github %} or locally using the command line.' redirect_from: - /articles/adding-wiki-pages-via-the-online-interface - /articles/editing-wiki-pages-via-the-online-interface @@ -47,7 +47,7 @@ Wikis are part of Git repositories, so you can make changes locally and push the ### Cloning wikis to your computer Every wiki provides an easy way to clone its contents down to your computer. -Once you've created an initial page on {% data variables.product.product_name %}, you can clone the repository to your computer with the provided URL: +Once you've created an initial page on {% data variables.product.github %}, you can clone the repository to your computer with the provided URL: ```shell $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.wiki.git diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index c7a22c514be3..00b149f0d7bb 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -43,7 +43,7 @@ Wikis can display PNG, JPEG, and GIF images. ### Linking to images in a repository -You can link to an image in a repository on {% data variables.product.product_name %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this: +You can link to an image in a repository on {% data variables.product.github %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this: [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md b/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md index 26c36654df32..087388c9e3e5 100644 --- a/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md +++ b/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md @@ -25,7 +25,7 @@ You can create a default code of conduct for your organization or personal accou ## Adding a code of conduct using a template -{% data variables.product.product_name %} provides templates for common codes of conduct to help you quickly add a code of conduct to your project. +{% data variables.product.github %} provides templates for common codes of conduct to help you quickly add a code of conduct to your project. {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} diff --git a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md index 8ccdfb7ff79d..e050abadcbe7 100644 --- a/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ b/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md @@ -18,13 +18,13 @@ shortTitle: Community health file Default community health files are a set of predefined files that provide guidance and templates for maintaining a healthy and collaborative open source project. These files help you automate and standardize various aspects of your project's development and community interaction, promoting transparency, good practices, and collaboration. -You can add default community health files to a public repository called `.github` and {% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in the following order: +You can add default community health files to a public repository called `.github` and {% data variables.product.github %} will use and display default files for any repository owned by the account that does not have its own file of that type in the following order: * The `.github` folder * The root of the repository * The `docs` folder -If no corresponding file is found in the current repository, {% data variables.product.product_name %} will use the default file from the `.github` repository, following the same order of precedence. +If no corresponding file is found in the current repository, {% data variables.product.github %} will use the default file from the `.github` repository, following the same order of precedence. For example, anyone who creates an issue or pull request in a repository that does not have its own `CONTRIBUTING.md` file will see a link to the default `CONTRIBUTING.md` from the `.github` repository. However, if a repository has any files in its own `.github/ISSUE_TEMPLATE` folder, such as issue templates or a `_config.yml` file, none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used. This allows repository maintainers to override the default files with specific templates or content on per-repository basis. diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index eb479765b73a..df4b6f78e354 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -66,7 +66,7 @@ You can encourage contributors to use issue templates by setting `blank_issues_e > [!NOTE] > If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your _config.yml_ file, the template in `issue_template.md` will be used when people choose to open a blank issue. If you disable blank issues, the template will never be used. -If you prefer to receive certain reports outside of {% data variables.product.product_name %}, you can direct people to external sites with `contact_links`. +If you prefer to receive certain reports outside of {% data variables.product.github %}, you can direct people to external sites with `contact_links`. Here is an example _config.yml_ file. diff --git a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/about-github-copilot-free.md b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/about-github-copilot-free.md index 13a3167df297..8a06ad545b0f 100644 --- a/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/about-github-copilot-free.md +++ b/content/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/about-github-copilot-free.md @@ -67,7 +67,7 @@ In {% data variables.product.prodname_vscode_shortname %} you can access {% data With {% data variables.product.prodname_copilot_free_short %}, you can ask {% data variables.product.prodname_copilot_short %} questions within a chat interface on {% data variables.product.github %}. -1. To access your personal dashboard once you're signed in, click the {% octicon "mark-github" aria-label="The github octocat logo" %} in the upper-left corner of any page on {% data variables.product.product_name %}. +1. To access your personal dashboard once you're signed in, click the {% octicon "mark-github" aria-label="The github octocat logo" %} in the upper-left corner of any page on {% data variables.product.github %}. 1. At the top of the dashboard, use the "Ask a question" box to start a chat with {% data variables.product.prodname_copilot_short %}. ### Other IDEs diff --git a/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 47826f0136c2..0befc83d91d8 100644 --- a/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -1,6 +1,6 @@ --- title: About discussions -intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.' +intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project.' versions: fpt: '*' ghes: '*' diff --git a/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 5fa63656e2f3..76a15b1dd2e8 100644 --- a/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -1,7 +1,7 @@ --- title: Collaborating with maintainers using discussions shortTitle: Collaborating with maintainers -intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.' +intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.github %} by communicating with the maintainers of the project in a discussion.' permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' diff --git a/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 01f96e743a9d..9533c1267bab 100644 --- a/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,6 +1,6 @@ --- title: Participating in a discussion -intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.' +intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.github %}.' permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' @@ -21,7 +21,7 @@ In addition to starting or viewing discussions and polls, you can: * React to comments with emoji * Upvote discussions and top-level comments to give them more visibility -{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/communities/maintaining-your-safety-on-github).{% endif %} +{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself. For more information, see [AUTOTITLE](/communities/maintaining-your-safety-on-github).{% endif %} ## Prerequisites diff --git a/content/discussions/guides/finding-your-discussions.md b/content/discussions/guides/finding-your-discussions.md index 86eee41d4baa..267ae2533817 100644 --- a/content/discussions/guides/finding-your-discussions.md +++ b/content/discussions/guides/finding-your-discussions.md @@ -15,12 +15,12 @@ redirect_from: {% ifversion global-nav-update %} 1. In the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "comment-discussion" aria-hidden="true" %} Discussions**. - ![Screenshot of the navigation bar on {% data variables.product.product_name %}. The "Open global navigation menu" icon is outlined in dark orange.](/assets/images/help/navigation/global-navigation-menu-icon.png) + ![Screenshot of the navigation bar on {% data variables.product.github %}. The "Open global navigation menu" icon is outlined in dark orange.](/assets/images/help/navigation/global-navigation-menu-icon.png) {% else %} 1. In the top-right corner of {% data variables.product.prodname_dotcom %}, click your profile photo, then click **Your discussions**. - ![Screenshot of the account dropdown on {% data variables.product.product_name %}. The "Your discussions" option is outlined in dark orange.](/assets/images/help/discussions/your-discussions.png) + ![Screenshot of the account dropdown on {% data variables.product.github %}. The "Your discussions" option is outlined in dark orange.](/assets/images/help/discussions/your-discussions.png) {% endif %} 1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. diff --git a/content/discussions/managing-discussions-for-your-community/index.md b/content/discussions/managing-discussions-for-your-community/index.md index 3b3b15f7cb99..c97a84750e01 100644 --- a/content/discussions/managing-discussions-for-your-community/index.md +++ b/content/discussions/managing-discussions-for-your-community/index.md @@ -1,7 +1,7 @@ --- title: Managing discussions for your community shortTitle: Managing discussions -intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools to moderate conversations among community members.' versions: fpt: '*' ghes: '*' diff --git a/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md index 73fe1ec1609d..912689cd3978 100644 --- a/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md +++ b/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md @@ -82,7 +82,7 @@ You can edit a section to change the section's emoji and title, and to add and r ## Deleting a category -When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. +When you delete a category, {% data variables.product.github %} will move all discussions in the deleted category to an existing category that you choose. When you delete a section, all categories within the section will no longer belong to a section. diff --git a/content/education/contribute-with-github-community-exchange/index.md b/content/education/contribute-with-github-community-exchange/index.md index caf08352b63d..c0deade414b0 100644 --- a/content/education/contribute-with-github-community-exchange/index.md +++ b/content/education/contribute-with-github-community-exchange/index.md @@ -1,7 +1,7 @@ --- title: Contribute with GitHub Community Exchange shortTitle: '{% data variables.product.prodname_community_exchange %}' -intro: 'With {% data variables.product.prodname_community_exchange %}, you can use {% data variables.product.product_name %} to contribute to open source and build your portfolio.' +intro: 'With {% data variables.product.prodname_community_exchange %}, you can use {% data variables.product.github %} to contribute to open source and build your portfolio.' versions: fpt: '*' children: diff --git a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher.md b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher.md index f7674318a3b6..05e3b34e3e90 100644 --- a/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher.md +++ b/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-teachers/apply-to-github-education-as-a-teacher.md @@ -22,7 +22,7 @@ shortTitle: Apply to GitHub Education {% data reusables.education.educator-requirements %} -For more information about personal accounts on {% data variables.product.product_name %}, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github). +For more information about personal accounts on {% data variables.product.github %}, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github). ## Applying to {% data variables.product.prodname_global_campus %} diff --git a/content/education/guides.md b/content/education/guides.md index 1ff203b4dd96..0e427a5d2ca5 100644 --- a/content/education/guides.md +++ b/content/education/guides.md @@ -1,15 +1,15 @@ --- title: Guides for GitHub Education -intro: 'These guides for {% data variables.product.prodname_education %} help you teach and learn both {% data variables.product.product_name %} and software development.' +intro: 'These guides for {% data variables.product.prodname_education %} help you teach and learn both {% data variables.product.github %} and software development.' allowTitleToDifferFromFilename: true versions: fpt: '*' shortTitle: Guides --- -## Get started with {% data variables.product.product_name %} +## Get started with {% data variables.product.github %} -Teachers, students, and researchers can use tools from {% data variables.product.product_name %} to enrich a software development curriculum and develop real-world collaboration skills. +Teachers, students, and researchers can use tools from {% data variables.product.github %} to enrich a software development curriculum and develop real-world collaboration skills. * [Sign up for a new {% data variables.product.prodname_dotcom %} account](/get-started/start-your-journey/creating-an-account-on-github) * [Git and {% data variables.product.prodname_dotcom %} quickstart](/get-started/start-your-journey) diff --git a/content/education/manage-coursework-with-github-classroom/index.md b/content/education/manage-coursework-with-github-classroom/index.md index b33fbb397a5c..c48d78d00b9c 100644 --- a/content/education/manage-coursework-with-github-classroom/index.md +++ b/content/education/manage-coursework-with-github-classroom/index.md @@ -1,7 +1,7 @@ --- title: Manage coursework with GitHub Classroom shortTitle: '{% data variables.product.prodname_classroom %}' -intro: 'With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development.' +intro: 'With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.github %} to administer or participate in a course about software development.' versions: fpt: '*' children: diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md index ab53915d5897..b5c66d3c4a23 100644 --- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md +++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md @@ -14,11 +14,11 @@ MakeCode Arcade is an online integrated development environment (IDE) for develo {% data reusables.classroom.readme-contains-button-for-online-ide %} -The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.github %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. -MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.github %} features like branches and pull requests. ## About submission of assignments with MakeCode Arcade diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 23644f41f466..96fdc57c1cc9 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -19,7 +19,7 @@ redirect_from: {% data reusables.classroom.about-assignments %} -You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams). +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.github %}. The visibility of the team is secret. Teams that you create on {% data variables.product.github %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams). {% data reusables.classroom.reuse-assignment-link %} @@ -43,7 +43,7 @@ Name your assignment, decide whether to assign a deadline, define teams, and cho ### Naming an assignment -For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.github %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. {% data reusables.classroom.assignments-type-a-title %} @@ -131,7 +131,7 @@ You can see the teams that are working on or have submitted an assignment in the ## Next steps -* After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see [AUTOTITLE](/get-started), [AUTOTITLE](/repositories), [AUTOTITLE](/get-started/using-git), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests), and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}. +* After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.github %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see [AUTOTITLE](/get-started), [AUTOTITLE](/repositories), [AUTOTITLE](/get-started/using-git), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests), and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}. * When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see [AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository). diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md index 56f2617ddb35..394c0690a367 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -10,7 +10,7 @@ redirect_from: shortTitle: Template repository --- -You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-template-repository). +You can use a template repository on {% data variables.product.github %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-template-repository). To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md index 53064d767462..12a2dc78e661 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md @@ -39,7 +39,7 @@ Name your assignment, decide whether to assign a deadline, and choose the visibi ### Naming an assignment -For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.github %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.github %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. {% data reusables.classroom.assignments-type-a-title %} @@ -119,7 +119,7 @@ You can see whether a student has joined the classroom and accepted or submitted ## Next steps -* Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see [AUTOTITLE](/get-started), [AUTOTITLE](/repositories), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests). +* Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.github %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see [AUTOTITLE](/get-started), [AUTOTITLE](/repositories), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests). * When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see [AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository). diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md index fb45bc53156c..c89e745383c6 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md @@ -15,27 +15,27 @@ redirect_from: ## About management of classrooms -{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.github %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}. -Invite TAs and admins to your classroom by inviting the personal accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) and [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). +Invite TAs and admins to your classroom by inviting the personal accounts on {% data variables.product.github %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) and [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom. {% data reusables.classroom.reuse-assignment-link %} -You can also view your classrooms and assignments directly from the {% data variables.product.product_name %} command line interface with the {% data variables.product.prodname_classroom %} extension. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli). +You can also view your classrooms and assignments directly from the {% data variables.product.github %} command line interface with the {% data variables.product.prodname_classroom %} extension. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli). ## About classroom rosters Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. -When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a personal account to link the personal account to an identifier for the classroom. After the student links a personal account, you can see the associated personal account in the roster. You can also see when the student accepts or submits an assignment. +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.github %} with a personal account to link the personal account to an identifier for the classroom. After the student links a personal account, you can see the associated personal account in the roster. You can also see when the student accepts or submits an assignment. ## Prerequisites -You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts#organization-accounts) and [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch). +You must have an organization account on {% data variables.product.github %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts#organization-accounts) and [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch). You must authorize the {% data variables.product.prodname_oauth_app %} for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see [AUTOTITLE](/apps/oauth-apps/using-oauth-apps/authorizing-oauth-apps). diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index f01eac66fac1..9c38e42ecbe9 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -48,11 +48,11 @@ Import the starter course into your organization, name your assignment, decide w ### Importing the assignment -To import the Git & {% data variables.product.product_name %} starter assignment into your organization, click **Import the assignment**. +To import the Git & {% data variables.product.github %} starter assignment into your organization, click **Import the assignment**. ### Naming the assignment -For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.github %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.github %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. {% data reusables.classroom.assignments-type-a-title %} diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli.md index 7e631f80ed9d..7f1c84d1a226 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli.md @@ -2,7 +2,7 @@ title: 'Using {% data variables.product.prodname_classroom %} with {% data variables.product.prodname_cli %}' shortTitle: '{% data variables.product.prodname_classroom %} CLI' allowTitleToDifferFromFilename: true -intro: 'You can use `gh`, the {% data variables.product.product_name %} command line interface, to work with {% data variables.product.prodname_classroom %} directly from your command line.' +intro: 'You can use `gh`, the {% data variables.product.github %} command line interface, to work with {% data variables.product.prodname_classroom %} directly from your command line.' versions: fpt: '*' type: how_to diff --git a/content/education/quickstart.md b/content/education/quickstart.md index 22adf1767dfe..009cd972c135 100644 --- a/content/education/quickstart.md +++ b/content/education/quickstart.md @@ -11,14 +11,14 @@ shortTitle: Quickstart Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. -In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. +In this guide, you'll get started with {% data variables.product.github %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. > [!TIP] > If you're a student and you'd like to take advantage of an academic discount, see [AUTOTITLE](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-education-for-students/apply-to-github-education-as-a-student). -## Creating accounts on {% data variables.product.product_name %} +## Creating accounts -First, you'll need to create a free personal account on {% data variables.product.product_name %}. +First, you'll need to create a free personal account on {% data variables.product.github %}. {% data reusables.accounts.create-account %} 1. Follow the prompts to create your free personal account. @@ -72,10 +72,10 @@ With your personal account and organization account, you're ready to get started ## Next steps -You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 +You've created a classroom, and you're ready to enrich your course with {% data variables.product.github %} and {% data variables.product.prodname_classroom %}! 🎉 * Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms). -* Use the Git and {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.product_name %} fundamentals. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment). +* Use the Git and {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.github %} fundamentals. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment). * Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} * Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding). * Participate in {% data variables.product.prodname_education_community_with_url %}. From a5903e01a32077d58e5a3fc5efbe368ea734d82b Mon Sep 17 00:00:00 2001 From: Anne-Marie <102995847+am-stead@users.noreply.github.com> Date: Tue, 21 Jan 2025 09:28:01 +0000 Subject: [PATCH 2/5] Hack Week 2025: update `product.product_name` in `/get-started` (iii) - last one (#54013) Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> --- .../accessibility/github-command-palette.md | 6 +-- .../managing-your-theme-settings.md | 4 +- ...-archive-of-your-personal-accounts-data.md | 8 ++-- ...ng-started-with-github-enterprise-cloud.md | 16 +++---- ...g-started-with-github-enterprise-server.md | 44 +++++++++---------- .../getting-started-with-github-team.md | 6 +-- content/get-started/using-git/about-git.md | 26 +++++------ content/get-started/using-git/index.md | 2 +- ...g-a-subfolder-out-into-a-new-repository.md | 4 +- ...hubs-services-from-a-restricted-network.md | 2 +- .../using-github/communicating-on-github.md | 6 +-- .../using-github/connecting-to-github.md | 38 ++++++++-------- .../get-started/using-github/github-mobile.md | 4 +- .../using-github/supported-browsers.md | 14 +++--- 14 files changed, 90 insertions(+), 90 deletions(-) diff --git a/content/get-started/accessibility/github-command-palette.md b/content/get-started/accessibility/github-command-palette.md index 97b71af6906d..2da3f760fd99 100644 --- a/content/get-started/accessibility/github-command-palette.md +++ b/content/get-started/accessibility/github-command-palette.md @@ -1,6 +1,6 @@ --- title: GitHub Command Palette -intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.' +intro: 'Use the command palette to navigate, search, and run commands directly from your keyboard.' versions: feature: command-palette shortTitle: GitHub Command Palette @@ -14,7 +14,7 @@ redirect_from: ## About the {% data variables.product.prodname_command_palette %} -You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard. +You can navigate, search, and run commands on {% data variables.product.github %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.github %}, which saves you time and keeps your hands on the keyboard. ### Fast navigation @@ -50,7 +50,7 @@ The default keyboard shortcuts used to open the command palette may conflict wit ## Navigating with the {% data variables.product.prodname_command_palette %} -You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. +You can use the command palette to navigate to any page that you have access to on {% data variables.product.github %}. {% data reusables.command-palette.open-palette %} diff --git a/content/get-started/accessibility/managing-your-theme-settings.md b/content/get-started/accessibility/managing-your-theme-settings.md index cdf45e673df2..ace15245fc9a 100644 --- a/content/get-started/accessibility/managing-your-theme-settings.md +++ b/content/get-started/accessibility/managing-your-theme-settings.md @@ -1,6 +1,6 @@ --- title: Managing your theme settings -intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.' +intro: 'You can manage how {% data variables.product.github %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.' versions: fpt: '*' ghes: '*' @@ -16,7 +16,7 @@ redirect_from: shortTitle: Manage theme settings --- -For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. +For choice and flexibility in how and when you use {% data variables.product.github %}, you can configure theme settings to change how {% data variables.product.github %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.github %} to follow your system settings. You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. diff --git a/content/get-started/archiving-your-github-personal-account-and-public-repositories/requesting-an-archive-of-your-personal-accounts-data.md b/content/get-started/archiving-your-github-personal-account-and-public-repositories/requesting-an-archive-of-your-personal-accounts-data.md index 8fd6145f651a..068b1cdb6078 100644 --- a/content/get-started/archiving-your-github-personal-account-and-public-repositories/requesting-an-archive-of-your-personal-accounts-data.md +++ b/content/get-started/archiving-your-github-personal-account-and-public-repositories/requesting-an-archive-of-your-personal-accounts-data.md @@ -15,11 +15,11 @@ topics: shortTitle: Request account archive --- -{% data variables.product.product_name %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through your account settings on {% data variables.product.prodname_dotcom %} or with the User Migration API. +{% data variables.product.github %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through your account settings on {% data variables.product.prodname_dotcom %} or with the User Migration API. -For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see [AUTOTITLE](/rest/migrations#download-a-user-migration-archive). +For more information about the data {% data variables.product.github %} stores that is available for exporting, see [AUTOTITLE](/rest/migrations#download-a-user-migration-archive). -When you request an export of your personal data through your account settings on {% data variables.product.prodname_dotcom %}, {% data variables.product.product_name %} packages your personal data in a `tar.gz` file and sends you an email to your primary email address with a download link. +When you request an export of your personal data through your account settings on {% data variables.product.github %}, {% data variables.product.github %} packages your personal data in a `tar.gz` file and sends you an email to your primary email address with a download link. By default, the download link expires after seven days. At any time before the download link expires, you can disable the link from your user settings. For more information, see [AUTOTITLE](/get-started/archiving-your-github-personal-account-and-public-repositories/requesting-an-archive-of-your-personal-accounts-data#deleting-access-to-an-archive-of-your-personal-accounts-data). @@ -32,7 +32,7 @@ The generated `tar.gz` file reflects the data stored at the time you started the {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %} 1. Under "Export account data", click **Start export** or **New export**. -1. Once the export is ready to download, {% data variables.product.product_name %} will send you a download link to your primary email address. +1. Once the export is ready to download, {% data variables.product.github %} will send you a download link to your primary email address. 1. Click the download link in your email and re-enter your password if prompted. 1. You'll be redirected to a `tar.gz` file that you can download. diff --git a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 7165d1ab1f61..632a507350ec 100644 --- a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -8,12 +8,12 @@ versions: This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an enterprise owner. -{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: +{% data variables.product.github %} provides two types of Enterprise products: * **{% data variables.product.prodname_ghe_cloud %}** * **{% data variables.product.prodname_ghe_server %}** -The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. +The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.github %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. {% data variables.product.prodname_ghe_cloud %} includes an enterprise account, which allows you to manage multiple organizations. You can choose to let enterprise members create and manage their own personal accounts, or you can use {% data variables.product.prodname_emus %}. For more information about {% data variables.product.prodname_ghe_cloud %}, see [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud). @@ -27,7 +27,7 @@ To get started with {% data variables.product.prodname_ghe_cloud %}, decide whic ### 2. About enterprise accounts -An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-your-enterprise-account/about-enterprise-accounts). +An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.github %} organizations, including member access, billing and usage and security. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-your-enterprise-account/about-enterprise-accounts). ### 3. Creating an enterprise account @@ -108,7 +108,7 @@ You can centrally manage access to your enterprise's resources from your IdP usi #### 3. Managing team synchronization -You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise). +You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.github %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise). #### 4. Enforcing policies for Advanced Security features in your enterprise account @@ -128,15 +128,15 @@ You can view actions from all of the organizations owned by your enterprise acco You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise). -## Part 5: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} +## Part 5: Customizing and automating your enterprise's work on {% data variables.product.github %} -Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% data variables.product.prodname_dotcom %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. +Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% data variables.product.github %} API, and existing {% data variables.product.github %} features to customize and automate your work. ### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 2. Using the {% data variables.product.github %} API {% data reusables.getting-started.api %} @@ -152,7 +152,7 @@ Members of your organization or enterprise can use tools from the {% data variab {% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) and [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages). -## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community +## Part 6: Participating in {% data variables.product.github %}'s community You and your enterprise members can use GitHub's learning and support resources to get the help they need. You can also support the open source community. diff --git a/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index 8acc8744c051..1ab0e5d501b3 100644 --- a/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -7,26 +7,26 @@ versions: This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator. -{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. +{% data variables.product.github %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. * **{% data variables.product.prodname_ghe_cloud %}** * **{% data variables.product.prodname_ghe_server %}** {% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider. -For more information about {% data variables.product.product_name %}, see [AUTOTITLE](/admin/overview/about-github-enterprise-server). +For more information about {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/overview/about-github-enterprise-server). -## Part 1: Installing {% data variables.product.product_name %} +## Part 1: Installing {% data variables.product.prodname_ghe_server %} -To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the {% data variables.enterprise.management_console %} for initial setup, configure your instance, and manage billing. +To get started, you will need to create your enterprise account, install the instance, use the {% data variables.enterprise.management_console %} for initial setup, configure your instance, and manage billing. ### 1. Creating your enterprise account -Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see [AUTOTITLE](/admin/managing-your-enterprise-account/about-enterprise-accounts). +Before you install {% data variables.product.prodname_ghe_server %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.github %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see [AUTOTITLE](/admin/managing-your-enterprise-account/about-enterprise-accounts). -### 2. Installing {% data variables.product.product_name %} +### 2. Installing {% data variables.product.prodname_ghe_server %} -To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance). +To get started, you will need to install the appliance on a virtualization platform of your choice. For more information, see [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance). ### 3. Using the {% data variables.enterprise.management_console %} @@ -36,7 +36,7 @@ You will use the {% data variables.enterprise.management_console %} to walk thro In addition to the {% data variables.enterprise.management_console %}, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see [AUTOTITLE](/admin/configuration). -You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings). +You can use the default network settings used by {% data variables.product.prodname_ghe_server %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings). ### 5. Configuring high availability @@ -52,7 +52,7 @@ To protect your production data, you can configure automated backups of {% data ### 8. Managing billing for your enterprise -Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see [AUTOTITLE](/billing/managing-your-github-billing-settings/about-billing-for-your-enterprise). +Billing for all the organizations and {% data variables.product.prodname_ghe_server %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see [AUTOTITLE](/billing/managing-your-github-billing-settings/about-billing-for-your-enterprise). ## Part 2: Organizing and managing your team @@ -96,7 +96,7 @@ To increase the security of {% data variables.location.product_location %}, you ### 1. Authenticating enterprise members -You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-identity-and-access-management). +You can use {% data variables.product.prodname_ghe_server %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-identity-and-access-management). You can also require two-factor authentication for each of your organizations. For more information, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization). @@ -115,18 +115,18 @@ You can implement required status checks and commit verifications to enforce you ### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features -You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see [AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise). +You can upgrade your {% data variables.product.prodname_ghe_server %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see [AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise). {% endif %} -## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} +## Part 4: Customizing and automating your enterprise's work on {% data variables.product.github %} -You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. +You can customize and automate work in organizations in your enterprise with {% data variables.product.github %} and {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_ghe_server %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. ### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} -You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see [AUTOTITLE](/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps). +You can build integrations with the {% data variables.product.prodname_ghe_server %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see [AUTOTITLE](/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps). -### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +### 2. Using the {% data variables.product.prodname_ghe_server %} API {% data reusables.getting-started.api %} @@ -136,7 +136,7 @@ You can build integrations with the {% ifversion fpt or ghec %}{% data variables {% data reusables.getting-started.actions %} -For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server). +For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server). ### 4. Publishing and managing {% data variables.product.prodname_registry %} @@ -149,17 +149,17 @@ For more information on enabling and configuring {% data variables.product.prodn {% data reusables.getting-started.github-pages-enterprise %} -## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources +## Part 5: Connecting with other {% data variables.product.github %} resources You can use {% data variables.product.prodname_github_connect %} to share resources. -If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see [AUTOTITLE](/admin/configuration/configuring-github-connect/managing-github-connect). +If you are the owner of both a {% data variables.product.prodname_ghe_server %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see [AUTOTITLE](/admin/configuration/configuring-github-connect/managing-github-connect). -## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +## Part 6: Using {% data variables.product.github %}'s learning and support resources -Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. +Your enterprise members can learn more about Git and {% data variables.product.github %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.github %} Enterprise Support. -### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} +### 1. Reading about {% data variables.product.prodname_ghe_server %} on {% data variables.product.prodname_docs %} You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see [AUTOTITLE](/get-started/using-github-docs/about-versions-of-github-docs). @@ -169,6 +169,6 @@ You can read documentation that reflects the features available with {% data var {% data reusables.getting-started.learning-enterprise %} -### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support +### 3. Working with {% data variables.product.github %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/content/get-started/onboarding/getting-started-with-github-team.md b/content/get-started/onboarding/getting-started-with-github-team.md index ef3296356164..fcdded5d00bf 100644 --- a/content/get-started/onboarding/getting-started-with-github-team.md +++ b/content/get-started/onboarding/getting-started-with-github-team.md @@ -83,7 +83,7 @@ You can help to make your organization more secure by recommending or requiring {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -## Part 5: Customizing and automating your work on {% data variables.product.product_name %} +## Part 5: Customizing and automating your work {% data reusables.getting-started.customizing-and-automating %} @@ -91,7 +91,7 @@ You can help to make your organization more secure by recommending or requiring {% data reusables.getting-started.marketplace %} -### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.github %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} API {% data reusables.getting-started.api %} @@ -103,7 +103,7 @@ You can help to make your organization more secure by recommending or requiring {% data reusables.getting-started.packages %} -## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community +## Part 6: Participating in {% data variables.product.github %}'s community {% data reusables.getting-started.participating-in-community %} diff --git a/content/get-started/using-git/about-git.md b/content/get-started/using-git/about-git.md index c8323e6ba9c2..7f45031f4e0b 100644 --- a/content/get-started/using-git/about-git.md +++ b/content/get-started/using-git/about-git.md @@ -1,6 +1,6 @@ --- title: About Git -intro: 'Learn about the version control system, Git, and how it works with {% data variables.product.product_name %}.' +intro: 'Learn about the version control system, Git, and how it works with {% data variables.product.github %}.' versions: fpt: '*' ghes: '*' @@ -36,17 +36,17 @@ In a distributed version control system, every developer has a full copy of the A repository, or Git project, encompasses the entire collection of files and folders associated with a project, along with each file's revision history. The file history appears as snapshots in time called commits. The commits can be organized into multiple lines of development called branches. Because Git is a DVCS, repositories are self-contained units and anyone who has a copy of the repository can access the entire codebase and its history. Using the command line or other ease-of-use interfaces, a Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more. -Through platforms like {% data variables.product.product_name %}, Git also provides more opportunities for project transparency and collaboration. Public repositories help teams work together to build the best possible final product. +Through platforms like {% data variables.product.github %}, Git also provides more opportunities for project transparency and collaboration. Public repositories help teams work together to build the best possible final product. -## How {% data variables.product.product_name %} works +## How {% data variables.product.github %} works -{% data variables.product.product_name %} hosts Git repositories and provides developers with tools to ship better code through command line features, issues (threaded discussions), pull requests, code review, or the use of a collection of free and for-purchase apps in the {% data variables.product.prodname_marketplace %}. With collaboration layers like the {% data variables.product.product_name %} flow, a community of 100 million developers, and an ecosystem with hundreds of integrations, {% data variables.product.product_name %} changes the way software is built. +{% data variables.product.github %} hosts Git repositories and provides developers with tools to ship better code through command line features, issues (threaded discussions), pull requests, code review, or the use of a collection of free and for-purchase apps in the {% data variables.product.prodname_marketplace %}. With collaboration layers like the {% data variables.product.github %} flow, a community of 100 million developers, and an ecosystem with hundreds of integrations, {% data variables.product.github %} changes the way software is built. -{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see [AUTOTITLE](/get-started/using-github/github-flow). +{% data variables.product.github %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.github %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see [AUTOTITLE](/get-started/using-github/github-flow). For {% data variables.product.prodname_dotcom %} plans and costs, see {% data variables.product.pricing_link %}. For information on how {% data variables.product.prodname_enterprise %} compares to other options, see [Comparing GitHub to other DevOps solutions](https://resources.github.com/devops/tools/compare/). -## {% data variables.product.product_name %} and the command line +## {% data variables.product.github %} and the command line ### Basic Git commands @@ -75,7 +75,7 @@ For more information, see the [full reference guide to Git commands](https://git ### Example: Contribute to an existing repository ```bash -# download a repository on {% data variables.product.product_name %} to our machine +# download a repository on {% data variables.product.github %} to our machine # Replace `owner/repo` with the owner and name of the repository to clone git clone https://github.com/owner/repo.git @@ -100,9 +100,9 @@ git commit -m "my snapshot" git push --set-upstream origin my-branch ``` -### Example: Start a new repository and publish it to {% data variables.product.product_name %} +### Example: Start a new repository and publish it to {% data variables.product.github %} -First, you will need to create a new repository on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/get-started/start-your-journey/hello-world). **Do not** initialize the repository with a README, .gitignore or License file. This empty repository will await your code. +First, you will need to create a new repository on {% data variables.product.github %}. For more information, see [AUTOTITLE](/get-started/start-your-journey/hello-world). **Do not** initialize the repository with a README, .gitignore or License file. This empty repository will await your code. ```bash # create a new directory, and initialize it with git-specific functions @@ -127,9 +127,9 @@ git remote add origin https://github.com/YOUR-USERNAME/YOUR-REPOSITORY-NAME.git git push --set-upstream origin main ``` -### Example: contribute to an existing branch on {% data variables.product.product_name %} +### Example: contribute to an existing branch on {% data variables.product.github %} -This example assumes that you already have a project called `repo` on the machine and that a new branch has been pushed to {% data variables.product.product_name %} since the last time changes were made locally. +This example assumes that you already have a project called `repo` on the machine and that a new branch has been pushed to {% data variables.product.github %} since the last time changes were made locally. ```bash # change into the `repo` directory @@ -155,11 +155,11 @@ git push ## Models for collaborative development -There are two primary ways people collaborate on {% data variables.product.product_name %}: +There are two primary ways people collaborate on {% data variables.product.github %}: 1. Shared repository 1. Fork and pull -With a shared repository, individuals and teams are explicitly designated as contributors with read, write, or administrator access. This simple permission structure, combined with features like protected branches, helps teams progress quickly when they adopt {% data variables.product.product_name %}. +With a shared repository, individuals and teams are explicitly designated as contributors with read, write, or administrator access. This simple permission structure, combined with features like protected branches, helps teams progress quickly when they adopt {% data variables.product.github %}. For an open source project, or for projects to which anyone can contribute, managing individual permissions can be challenging, but a fork and pull model allows anyone who can view the project to contribute. A fork is a copy of a project under a developer's personal account. Every developer has full control of their fork and is free to implement a fix or a new feature. Work completed in forks is either kept separate, or is surfaced back to the original project via a pull request. There, maintainers can review the suggested changes before they're merged. For more information, see [AUTOTITLE](/get-started/exploring-projects-on-github/contributing-to-a-project). diff --git a/content/get-started/using-git/index.md b/content/get-started/using-git/index.md index e2d8c67c556d..b3e0b86c6fd0 100644 --- a/content/get-started/using-git/index.md +++ b/content/get-started/using-git/index.md @@ -1,6 +1,6 @@ --- title: Using Git -intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.' +intro: 'Use Git to manage your {% data variables.product.github %} repositories from your computer.' redirect_from: - /articles/using-common-git-commands - /github/using-git/using-common-git-commands diff --git a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 56d27f864e99..0c613d99b217 100644 --- a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -59,7 +59,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist # Filter the specific branch by using a single sub-directory as the root for the new repository ``` -1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.product_name %}. +1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.github %}. 1. At the top of your new repository on {% data variables.product.prodname_dotcom %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL. @@ -83,7 +83,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist > origin https://{% data variables.product.product_url %}/USERNAME/NEW-REPOSITORY-NAME.git (push) ``` -1. Push your changes to the new repository on {% data variables.product.product_name %}. +1. Push your changes to the new repository on {% data variables.product.github %}. ```shell git push -u origin BRANCH-NAME diff --git a/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md b/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md index 54edff83bc7a..f10e2afcd710 100644 --- a/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md +++ b/content/get-started/using-github/allowing-access-to-githubs-services-from-a-restricted-network.md @@ -7,7 +7,7 @@ versions: shortTitle: Allow network access --- -## About access to {% data variables.product.product_name %} from a restricted network +## About access to {% data variables.product.github %} from a restricted network In rare cases, an institution's network access policy may restrict access to specific domain names for end users. For example, the policy may use DNS filtering to deny access to sites like {% data variables.product.prodname_dotcom %}. If your institution requires this level of control, but you still want to permit access to services on {% data variables.product.prodname_dotcom %}, you can create exceptions in your policy to allow access to the necessary domains. diff --git a/content/get-started/using-github/communicating-on-github.md b/content/get-started/using-github/communicating-on-github.md index 420318410298..4c8f8c763b89 100644 --- a/content/get-started/using-github/communicating-on-github.md +++ b/content/get-started/using-github/communicating-on-github.md @@ -1,6 +1,6 @@ --- title: Communicating on GitHub -intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.' +intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.github %}.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github - /articles/about-discussions-in-issues-and-pull-requests @@ -20,7 +20,7 @@ topics: --- ## Introduction -{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs. +{% data variables.product.github %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs. {% ifversion team-discussions %} You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have. @@ -171,7 +171,7 @@ To ask a question about an issue or discussion: ## Next steps -These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. +These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.github %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues#working-with-issues) and [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates). diff --git a/content/get-started/using-github/connecting-to-github.md b/content/get-started/using-github/connecting-to-github.md index b518b3285181..fabc9a386acc 100644 --- a/content/get-started/using-github/connecting-to-github.md +++ b/content/get-started/using-github/connecting-to-github.md @@ -1,6 +1,6 @@ --- title: Connecting to GitHub -intro: 'Learn about the tools you can use to work with repositories hosted on {% data variables.product.prodname_dotcom %}.' +intro: 'Learn about the tools you can use to work with repositories hosted on {% data variables.product.github %}.' versions: fpt: '*' ghec: '*' @@ -15,20 +15,20 @@ topics: ## Introduction -{% data variables.product.prodname_dotcom %} is a web-based app that lets you host files in repositories, collaborate on work, and track changes to files over time. Version tracking on {% data variables.product.prodname_dotcom %} is powered by the open source software Git. Whenever you update a repository on {% data variables.product.prodname_dotcom %}, Git tracks the changes you make. +{% data variables.product.github %} is a web-based app that lets you host files in repositories, collaborate on work, and track changes to files over time. Version tracking on {% data variables.product.github %} is powered by the open source software Git. Whenever you update a repository on {% data variables.product.github %}, Git tracks the changes you make. -There are many ways to work with {% data variables.product.prodname_dotcom %}, and you can choose a method that suits your level of experience, personal preferences, and the repositories you work with. For example, you can choose whether you want to work in the browser or from your desktop, how you want to use Git, and what capabilities you need from your editor and other software. You may choose to work with different repositories in different ways. +There are many ways to work with {% data variables.product.github %}, and you can choose a method that suits your level of experience, personal preferences, and the repositories you work with. For example, you can choose whether you want to work in the browser or from your desktop, how you want to use Git, and what capabilities you need from your editor and other software. You may choose to work with different repositories in different ways. -If you're new to {% data variables.product.prodname_dotcom %}, a good way to start contributing is to make changes in the browser on {% data variables.location.product_location %}. As you become more familiar with {% data variables.product.prodname_dotcom %} and start contributing larger changes, you may want to start working with other tools. This article explains how to progress through these stages and helps you choose the best tool for your requirements at each stage. To quickly compare all the tools available for working with {% data variables.product.prodname_dotcom %}, see [Comparison of tools for connecting to {% data variables.product.prodname_dotcom %}](#comparison-of-tools-for-connecting-to-github). +If you're new to {% data variables.product.github %}, a good way to start contributing is to make changes in the browser on {% data variables.location.product_location %}. As you become more familiar with {% data variables.product.github %} and start contributing larger changes, you may want to start working with other tools. This article explains how to progress through these stages and helps you choose the best tool for your requirements at each stage. To quickly compare all the tools available for working with {% data variables.product.github %}, see [Comparison of tools for connecting to {% data variables.product.github %}](#comparison-of-tools-for-connecting-to-github). ## Getting started -In the user interface on {% data variables.location.product_location %}, you can perform the whole "{% data variables.product.prodname_dotcom %} flow" for contributing to a repository, including creating a branch or fork, editing and previewing files, committing your changes, and creating a pull request. You can also upload files from your computer or download them from the repository. For more information, see [AUTOTITLE](/get-started/using-github/github-flow). +In the user interface on {% data variables.location.product_location %}, you can perform the whole "{% data variables.product.github %} flow" for contributing to a repository, including creating a branch or fork, editing and previewing files, committing your changes, and creating a pull request. You can also upload files from your computer or download them from the repository. For more information, see [AUTOTITLE](/get-started/using-github/github-flow). Working directly on {% data variables.location.product_location %} is often the quickest way to contribute to a repository, for the following reasons. -* You're working directly with the repository hosted on {% data variables.product.prodname_dotcom %}, so you don't have to download a copy of the repository to your computer and keep this copy in sync. -* If you're already signed in to {% data variables.product.prodname_dotcom %}, you have access to any repository where you have the necessary permissions, so you don't need to set up any additional authentication on your computer. +* You're working directly with the repository hosted on {% data variables.product.github %}, so you don't have to download a copy of the repository to your computer and keep this copy in sync. +* If you're already signed in to {% data variables.product.github %}, you have access to any repository where you have the necessary permissions, so you don't need to set up any additional authentication on your computer. * You can commit changes in the user interface, so you don't need to use the command line or memorize any Git commands. For a tutorial to help you get started with making changes in the browser, see [AUTOTITLE](/get-started/start-your-journey/hello-world). @@ -42,31 +42,31 @@ Working directly on {% data variables.location.product_location %} is best for s * If you want an editor where you can quickly open or create files, you can press the `.` key in any repository to open the github.dev editor. This is a lightweight web-based editor that includes many of the features of {% data variables.product.prodname_vscode %}, such as a search bar and buttons for Git commands. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor). * If you want to stay in the browser but need to do things like run commands, create a test build of your project, or install dependencies, you can open a repository in a codespace. A codespace is a remote development environment with storage and compute power. It includes an editor and integrated terminal, and comes preinstalled with common tools you may need to work with a project, including Git. For more information, see [AUTOTITLE](/codespaces/overview). -Alternatively, you can connect to {% data variables.product.prodname_dotcom %} from your desktop, and work with a local copy of the repository.{% else %}Working directly in the browser is best for small, simple changes, often targeting a single file in a repository. If you want to make more complex changes, you may need to connect to {% data variables.product.prodname_dotcom %} from the desktop, and work with a local copy of the repository.{% endif %} +Alternatively, you can connect to {% data variables.product.github %} from your desktop, and work with a local copy of the repository.{% else %}Working directly in the browser is best for small, simple changes, often targeting a single file in a repository. If you want to make more complex changes, you may need to connect to {% data variables.product.github %} from the desktop, and work with a local copy of the repository.{% endif %} ## Working from the desktop -To work with a repository from your desktop, you'll need to download (or "clone") a copy of the repository to your computer, then push any changes you make to {% data variables.product.prodname_dotcom %}. Working from your desktop can have several advantages over working in the browser. +To work with a repository from your desktop, you'll need to download (or "clone") a copy of the repository to your computer, then push any changes you make to {% data variables.product.github %}. Working from your desktop can have several advantages over working in the browser. * You can work with all your local files and tools. * You have access to compute power. For example, you might need to run a script to create a local preview of a site, so you can test the changes you're making. * You don't need an Internet connection to work on a project. -If you haven't worked with a {% data variables.product.prodname_dotcom %} repository from your desktop before, you'll need to authenticate to {% data variables.product.prodname_dotcom %} from your computer, so you can access the repositories you need. You may also need to set up your working environment with the tools you need to contribute, such as Git, an editor, and dependencies for a project. For these reasons, it can take longer to get started if you want to work from your desktop, compared to working in the browser. +If you haven't worked with a {% data variables.product.github %} repository from your desktop before, you'll need to authenticate to {% data variables.product.github %} from your computer, so you can access the repositories you need. You may also need to set up your working environment with the tools you need to contribute, such as Git, an editor, and dependencies for a project. For these reasons, it can take longer to get started if you want to work from your desktop, compared to working in the browser. -There are several tools you can use to connect to {% data variables.product.prodname_dotcom %} from your desktop. These tools allow you to authenticate to {% data variables.product.prodname_dotcom %}, clone a repository, track your changes, and push the changes to {% data variables.product.prodname_dotcom %}. +There are several tools you can use to connect to {% data variables.product.github %} from your desktop. These tools allow you to authenticate to {% data variables.product.github %}, clone a repository, track your changes, and push the changes to {% data variables.product.github %}. -* If you want a lot of control and flexibility, you can use the command line. You'll need to install Git and be familiar with some basic Git commands. You can also install {% data variables.product.prodname_cli %}, a command-line interface that lets you perform many actions on {% data variables.product.prodname_dotcom %}, such as creating a pull request or forking a repository. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/set-up-git) and [AUTOTITLE](/github-cli/github-cli/about-github-cli). +* If you want a lot of control and flexibility, you can use the command line. You'll need to install Git and be familiar with some basic Git commands. You can also install {% data variables.product.prodname_cli %}, a command-line interface that lets you perform many actions on {% data variables.product.github %}, such as creating a pull request or forking a repository. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/set-up-git) and [AUTOTITLE](/github-cli/github-cli/about-github-cli). * If you'd prefer to use a visual interface, you can use a visual Git client such as {% data variables.product.prodname_desktop %}. With {% data variables.product.prodname_desktop %}, you can visualize the changes you're making and access most Git commands through a visual interface, so you don't need to memorize any commands. For more information, see [AUTOTITLE](/desktop/overview/about-github-desktop). -* If you want to work in one place, you can often do most things from your editor. An editor such as {% data variables.product.prodname_vscode_shortname %} includes an integrated terminal and buttons for common Git commands, so you can edit files and push your changes to {% data variables.product.prodname_dotcom %} all from one place. You can also install an extension to work directly with pull requests and issues on {% data variables.product.prodname_dotcom %}. To get started, see [Download {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/download). +* If you want to work in one place, you can often do most things from your editor. An editor such as {% data variables.product.prodname_vscode_shortname %} includes an integrated terminal and buttons for common Git commands, so you can edit files and push your changes to {% data variables.product.github %} all from one place. You can also install an extension to work directly with pull requests and issues on {% data variables.product.github %}. To get started, see [Download {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/download). -## Comparison of tools for connecting to {% data variables.product.prodname_dotcom %} +## Comparison of tools for connecting to {% data variables.product.github %} -The following table provides a comparison between the tools you can use to work with repositories on {% data variables.product.prodname_dotcom %}, both in your browser and from your desktop. +The following table provides a comparison between the tools you can use to work with repositories on {% data variables.product.github %}, both in your browser and from your desktop. -You can perform the whole {% data variables.product.prodname_dotcom %} flow with any of the tools described here. Each tool includes access not only to Git commands for tracking the changes you've made, but also to {% data variables.product.prodname_dotcom %}-specific features, so you can create a pull request with your proposed changes from wherever you're working. +You can perform the whole {% data variables.product.github %} flow with any of the tools described here. Each tool includes access not only to Git commands for tracking the changes you've made, but also to {% data variables.product.github %}-specific features, so you can create a pull request with your proposed changes from wherever you're working. -For more information about how to authenticate to {% data variables.product.product_name %} with each of these tools, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github). +For more information about how to authenticate to {% data variables.product.github %} with each of these tools, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github). | Tool | Use case | Browser or desktop | | ---- | -------- | ------------------ | @@ -75,10 +75,10 @@ For more information about how to authenticate to {% data variables.product.prod | **github.dev** | You want to make more complex changes to a repository than is possible on {% data variables.product.prodname_dotcom_the_website %}, but don't need to work with a terminal or tools you have installed on your computer. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-the-githubdev-editor). | Browser | | **{% data variables.product.prodname_github_codespaces %}** | You need the resources of a computer to do things like run scripts, create a test build of your project, or install dependencies, and you want to get started quickly by working in a cloud-based environment. For more information, see [AUTOTITLE](/codespaces/overview). | Browser or desktop | | {% endif %} | -| **{% data variables.product.prodname_desktop %}** | You want to work with files locally, and would prefer a visual interface to use Git, visualize changes, and interact with {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/desktop/overview/about-github-desktop). | Desktop | +| **{% data variables.product.prodname_desktop %}** | You want to work with files locally, and would prefer a visual interface to use Git, visualize changes, and interact with {% data variables.product.github %}. For more information, see [AUTOTITLE](/desktop/overview/about-github-desktop). | Desktop | | **IDE or text editor** | You're working with more complex files and projects and want everything in one place. | Desktop | | **Command-line Git and {% data variables.product.prodname_cli %}** | You're used to working from the command line and want to avoid switching context, or you need to access a complex Git command that isn't integrated into visual interfaces. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/set-up-git) and [AUTOTITLE](/github-cli/github-cli/about-github-cli). | Desktop | -| **{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API** | You want to automate common tasks such as backing up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/rest/about-the-rest-api/comparing-githubs-rest-api-and-graphql-api). | Browser or desktop | +| **{% ifversion fpt or ghec %}{% data variables.product.github %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} API** | You want to automate common tasks such as backing up your data, or create integrations that extend {% data variables.product.github %}. For more information, see [AUTOTITLE](/rest/about-the-rest-api/comparing-githubs-rest-api-and-graphql-api). | Browser or desktop | ## Further reading diff --git a/content/get-started/using-github/github-mobile.md b/content/get-started/using-github/github-mobile.md index 2fecc0395e75..dc2c63f12dc7 100644 --- a/content/get-started/using-github/github-mobile.md +++ b/content/get-started/using-github/github-mobile.md @@ -1,6 +1,6 @@ --- title: GitHub Mobile -intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' +intro: 'Triage, collaborate, and manage your work on {% data variables.product.github %} from your mobile device.' shortTitle: GitHub Mobile versions: fpt: '*' @@ -18,7 +18,7 @@ redirect_from: {% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.github %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your data through a trusted, first-party client application. With {% data variables.product.prodname_mobile %} you can: diff --git a/content/get-started/using-github/supported-browsers.md b/content/get-started/using-github/supported-browsers.md index 23e6ad1ddda6..e95f3c6e99bd 100644 --- a/content/get-started/using-github/supported-browsers.md +++ b/content/get-started/using-github/supported-browsers.md @@ -6,36 +6,36 @@ redirect_from: - /articles/supported-browsers - /github/getting-started-with-github/supported-browsers - /github/getting-started-with-github/using-github/supported-browsers -intro: 'For the best experience with {% data variables.product.product_name %}, we recommend using the latest version of [Chrome](https://google.com/chrome), [Edge](https://www.microsoft.com/en-us/edge), [Firefox](https://mozilla.org/firefox), or [Safari](https://apple.com/safari).' +intro: 'For the best experience with {% data variables.product.github %}, we recommend using the latest version of [Chrome](https://google.com/chrome), [Edge](https://www.microsoft.com/en-us/edge), [Firefox](https://mozilla.org/firefox), or [Safari](https://apple.com/safari).' versions: fpt: '*' ghes: '*' ghec: '*' --- -## About web browser support for {% data variables.product.product_name %} +## About web browser support -We design {% data variables.product.product_name %} with the latest web browsers in mind. We recommend that you use the latest version of one of the following browsers. +We design {% data variables.product.github %} with the latest web browsers in mind. We recommend that you use the latest version of one of the following browsers. * [Apple Safari](https://apple.com/safari) * [Google Chrome](https://google.com/chrome) * [Microsoft Edge](https://www.microsoft.com/en-us/edge) * [Mozilla Firefox](https://mozilla.org/firefox) -If you do not use the latest version of a recommended browser, or if you use a browser that is not listed above, {% data variables.product.product_name %} or some features may not work as you expect, or at all. +If you do not use the latest version of a recommended browser, or if you use a browser that is not listed above, {% data variables.product.github %} or some features may not work as you expect, or at all. For more information about how we maintain browser compatibility for {% data variables.product.company_short %}'s products, see the [`github/browser-support`](https://github.com/github/browser-support) repository. ## Extended support for recommended web browsers -Some browser vendors provide extended support releases. We do our best to ensure that {% data variables.product.product_name %} functions properly in the latest extended support release for: +Some browser vendors provide extended support releases. We do our best to ensure that {% data variables.product.github %} functions properly in the latest extended support release for: * Chrome's [extended stable channel](https://support.google.com/chrome/a/answer/9027636) * Edge's [Extended Stable Channel](https://docs.microsoft.com/en-gb/deployedge/microsoft-edge-channels#extended-stable-channel) * Firefox's [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) -In earlier extended support releases, {% data variables.product.product_name %} may not work as you expect, and some features may not be available. +In earlier extended support releases, {% data variables.product.github %} may not work as you expect, and some features may not be available. ## {% data variables.release-phases.public_preview_caps %} and developer builds -You may encounter unexpected bugs in {% data variables.release-phases.public_preview %} and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer. +You may encounter unexpected bugs in {% data variables.release-phases.public_preview %} and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.github %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer. From c933e1efe361867ad8574eca8b50f7a1d79e4cf6 Mon Sep 17 00:00:00 2001 From: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Date: Tue, 21 Jan 2025 09:43:55 +0000 Subject: [PATCH 3/5] Remove `product_name` from `organizations` directory (#54020) --- .../about-your-organizations-news-feed.md | 2 +- .../customizing-your-organizations-profile.md | 2 +- .../about-team-discussions.md | 2 +- ...embers-saml-access-to-your-organization.md | 6 ++--- ...-in-the-audit-log-for-your-organization.md | 4 ++-- ...tor-authentication-in-your-organization.md | 4 ++-- .../about-ssh-certificate-authorities.md | 4 ++-- .../adding-people-to-your-organization.md | 2 +- ...ember-information-for-your-organization.md | 2 +- ...ng-a-former-member-of-your-organization.md | 2 +- ...it-signoff-policy-for-your-organization.md | 4 ++-- ...e-for-repositories-in-your-organization.md | 2 +- ...ess-management-with-saml-single-sign-on.md | 2 +- .../about-scim-for-organizations.md | 4 ++-- ...f-your-identity-provider-is-unavailable.md | 2 +- ...-identity-provider-to-your-organization.md | 6 ++--- ...ions-saml-single-sign-on-recovery-codes.md | 6 ++--- ...m-synchronization-for-your-organization.md | 4 ++-- .../about-custom-repository-roles.md | 2 +- .../about-teams.md | 2 +- ...-a-team-with-an-identity-provider-group.md | 24 +++++++++---------- 21 files changed, 44 insertions(+), 44 deletions(-) diff --git a/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md index edb60578367c..7e5cba0c312e 100644 --- a/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md +++ b/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -22,7 +22,7 @@ shortTitle: Organization news feed {% endif %} -An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}. +An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.github %}. ## Accessing your organization's news feed diff --git a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index a36d1817b7b8..8986c103a20b 100644 --- a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -83,7 +83,7 @@ You can pin repositories that you want to feature, such as those that are freque ## Changing your organization's profile picture -When you create an organization, {% data variables.product.product_name %} provides you with a randomly generated "identicon." The identicon is generated from a hash of your organization's user ID, so there's no way to control its color or pattern. +When you create an organization, {% data variables.product.github %} provides you with a randomly generated "identicon." The identicon is generated from a hash of your organization's user ID, so there's no way to control its color or pattern. You can replace the identicon with an image that represents your organization. To replace the image, you can upload a new image or use a Gravatar image. diff --git a/content/organizations/collaborating-with-your-team/about-team-discussions.md b/content/organizations/collaborating-with-your-team/about-team-discussions.md index 4c3cd972087f..95c33e4864b2 100644 --- a/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -26,7 +26,7 @@ You can link to any team discussion to reference it elsewhere. You can pin impor When someone posts or replies to a public discussion on a team's page, members of the team and members of any child teams receive email or web notifications. When someone posts or replies to a private discussion on a team's page, only members of the team receive notifications. > [!TIP] -> Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications). +> Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.github %}, or both. For more information, see [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications). By default, if your username is mentioned in a team discussion, you'll receive notifications for the post mentioning your username and any replies to that post. Also, by default, if you reply to a post, you will receive notifications for other replies to the post. diff --git a/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index c22c8cafcc4e..63c0f93b5d55 100644 --- a/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -16,7 +16,7 @@ shortTitle: Manage SAML access ## About SAML access to your organization -When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.prodname_dotcom %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with your organization. +When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.github %}. To access your organization's resources on {% data variables.product.github %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with your organization. You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page. @@ -28,9 +28,9 @@ When available, the entry will include SCIM data. For more information, see [AUT > [!WARNING] > For organizations using SCIM: -> * Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +> * Revoking a linked user identity on {% data variables.product.github %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. > * An admin must revoke a linked identity through the identity provider. -> * To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. +> * To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.prodname_ghe_cloud %} application. For more information, see your identity provider's documentation. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization.md index 680edd3d91aa..0e32013c20bf 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization.md @@ -18,7 +18,7 @@ topics: ## About display of IP addresses in the audit log -By default, {% data variables.product.product_name %} does not display the source IP address for events in your organization's audit log. {% data reusables.audit_log.about-ip-display %} If you enable this setting, the IP address will be displayed for **new and existing events** in the audit log. +By default, {% data variables.product.github %} does not display the source IP address for events in your organization's audit log. {% data reusables.audit_log.about-ip-display %} If you enable this setting, the IP address will be displayed for **new and existing events** in the audit log. You are responsible for meeting any legal obligations that accompany the viewing or storage of IP addresses displayed within your organization's audit log. @@ -34,7 +34,7 @@ After you enable the feature, you can access the audit log to view events that i ## Events that display IP addresses in the audit log -{% data variables.product.product_name %} displays an IP address for each event in the organization audit log that meets these criteria. +{% data variables.product.github %} displays an IP address for each event in the organization audit log that meets these criteria. * The actor is an organization member or owner * The target is either an organization-owned repository that is private or internal, or an organization resource that is not a repository, such as a project. diff --git a/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md index 865ec7f94ddb..4a20548e62fb 100644 --- a/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md @@ -22,7 +22,7 @@ product: 'Requiring two-factor authentication is available to organizations on a ## About two-factor authentication for organizations -{% data reusables.two_fa.about-2fa %} You can require all {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} in your organization to enable two-factor authentication on {% data variables.product.product_name %}. For more information about two-factor authentication, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa). +{% data reusables.two_fa.about-2fa %} You can require all {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} in your organization to enable two-factor authentication on {% data variables.product.github %}. For more information about two-factor authentication, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa). {% ifversion fpt or ghec %} @@ -52,7 +52,7 @@ You can also require two-factor authentication for organizations in an enterpris ## Prerequisites -Before you can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to use two-factor authentication, you must enable 2FA for your account on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa). +Before you can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to use two-factor authentication, you must enable 2FA for your account. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa). Before you require use of two-factor authentication, we recommend notifying {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} and asking them to set up 2FA for their accounts. You can see if members and outside collaborators already use 2FA. For more information, see [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled). diff --git a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index ef0e72b4d7c1..59425690e576 100644 --- a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -27,7 +27,7 @@ Certificates added to your enterprise grant access to all organizations owned by Optionally, you can require that members and outside collaborators use SSH certificates to access organization resources. For more information, see [AUTOTITLE](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities) and [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise). -For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. +For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.github %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. {% ifversion ghec %} Organization contributors can use their signed certificates for authentication even if you've enforced SAML single sign-on (SSO), without the need to authorize the signed certificates. @@ -47,7 +47,7 @@ If your organization doesn't require SSH certificates, contributors can continue ## Issuing certificates -When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. You can reference the user using their login handle{% ifversion ssh-ca-expires %} or their user ID{% endif %}. For example, you can use OpenSSH's `ssh-keygen` command, replacing KEY-IDENTITY with your key identity and USERNAME with a {% data variables.product.product_name %} username{% ifversion ssh-ca-expires %} or user ID{% endif %}. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate. +When you issue each certificate, you must include an extension that specifies which {% data variables.product.github %} user the certificate is for. You can reference the user using their login handle{% ifversion ssh-ca-expires %} or their user ID{% endif %}. For example, you can use OpenSSH's `ssh-keygen` command, replacing KEY-IDENTITY with your key identity and USERNAME with a {% data variables.product.github %} username{% ifversion ssh-ca-expires %} or user ID{% endif %}. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate. > [!NOTE] > You must update to OpenSSH 7.6 or later to use these commands. diff --git a/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md index f4a165152afa..51ad3672ea6f 100644 --- a/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -1,6 +1,6 @@ --- title: Adding people to your organization -intro: 'You can make anyone a member of your organization using their {% data variables.product.product_name %} username or email address.' +intro: 'You can make anyone a member of your organization using their {% data variables.product.github %} username or email address.' redirect_from: - /articles/adding-people-to-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization diff --git a/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md index 8eaaebe39218..a17dac19d0c8 100644 --- a/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md @@ -60,7 +60,7 @@ You may be able to view the email addresses for members of your organization on If SAML SSO is configured for your organization, or if you have verified a domain, you may be able to view the email addresses in one or more of the following ways. -1. On your SAML Identity Provider (IdP), review the email addresses of users with access to {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam). +1. On your SAML Identity Provider (IdP), review the email addresses of users with access to {% data variables.product.github %}. For more information, see [AUTOTITLE](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam). 1. Export the membership report for your organization. The report may contain the user's email address, stored as the following values. * `saml_name_id`: The `NameID` from the user's linked SAML identity, which is typically the user's email address (for more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)) diff --git a/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md index 870b50440114..9e885a1b843e 100644 --- a/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -51,7 +51,7 @@ When you reinstate a former organization member, the following items can be rest The correct way to reinstate a former member depends on your organization's identity and access management configuration. -* If the user was removed via SCIM because they were unassigned from the {% data variables.product.product_name %} application in your IdP, re-invite the user via SCIM by re-assigning them to the application. The user's organization membership will be reinstated after they sign into {% data variables.product.prodname_dotcom %} and accept the invitation. +* If the user was removed via SCIM because they were unassigned from the {% data variables.product.prodname_ghe_cloud %} application in your IdP, re-invite the user via SCIM by re-assigning them to the application. The user's organization membership will be reinstated after they sign into {% data variables.product.prodname_dotcom %} and accept the invitation. * If your organization uses SAML but not SCIM, ask the user to authenticate via SAML single sign-on, via your IP or by signing into {% data variables.product.prodname_dotcom %}, navigating to the organization, and clicking the banner to authenticate via SAML single sign-on. The user's organization membership will be reinstated after they successfully authenticate. * Otherwise, invite the user to rejoin your organization on {% data variables.product.prodname_dotcom %}, following the steps below. diff --git a/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md index f4c145018038..3106e72732dd 100644 --- a/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md +++ b/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md @@ -1,6 +1,6 @@ --- title: Managing the commit signoff policy for your organization -intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.' +intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.github %}''s web interface to repositories owned by your organization.' versions: fpt: '*' ghec: '*' @@ -13,7 +13,7 @@ shortTitle: Manage the commit signoff policy ## About commit signoffs -To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author. +To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.github %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through the web interface will automatically be signed off on by the commit author. People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository). diff --git a/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md index db2b1a00d643..f92c456a907c 100644 --- a/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -16,7 +16,7 @@ shortTitle: Manage default branch name ## About management of the default branch name -When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch). +When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.github %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch). {% data reusables.branches.change-default-branch %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index cfd6d52a0203..2799af85bdf1 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -38,7 +38,7 @@ The first time a member uses SAML SSO to access your organization, {% data varia If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see [AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility). -Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. +Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.company_short %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. {% data reusables.saml.saml-single-logout-not-supported %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md index 36da3a0fe638..ccb945034cf1 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md @@ -14,7 +14,7 @@ topics: ## About SCIM for organizations -If your organization uses [SAML SSO](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on), you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. +If your organization uses [SAML SSO](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on), you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.github %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. {% data reusables.saml.ghec-only %} @@ -26,7 +26,7 @@ If you use SAML SSO without implementing SCIM, you won't have automatic deprovis ## Supported identity providers -These identity providers (IdPs) are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [AUTOTITLE](/rest/scim). +These identity providers (IdPs) are compatible with the {% data variables.product.github %} SCIM API for organizations. For more information, see [AUTOTITLE](/rest/scim). * Microsoft Entra ID (previously known as Azure AD) * Okta * OneLogin diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md index cb07f6ac4974..d3bb2548da0f 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -1,6 +1,6 @@ --- title: Accessing your organization if your identity provider is unavailable -intro: 'Organization owners can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on (SSO) and using their recovery codes.' +intro: 'Organization owners can sign into {% data variables.product.github %} even if their identity provider is unavailable by bypassing single sign-on (SSO) and using their recovery codes.' redirect_from: - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index f27abdcbc38a..e8135a0c3288 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -1,6 +1,6 @@ --- title: Connecting your identity provider to your organization -intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider (IdP) to your organization on {% data variables.product.product_name %}.' +intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider (IdP) to your organization on {% data variables.product.github %}.' redirect_from: - /articles/connecting-your-identity-provider-to-your-organization - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization @@ -15,7 +15,7 @@ shortTitle: Connect an IdP ## About connection of your IdP to your organization -When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization). +When you enable SAML SSO for your {% data variables.product.github %} organization, you connect your identity provider (IdP) to your organization. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization). {% data reusables.saml.ghec-only %} @@ -28,7 +28,7 @@ You can find the SAML and SCIM implementation details for your IdP in the IdP's * Shibboleth [SAML](https://shibboleth.atlassian.net/wiki/spaces/IDP4/overview) > [!NOTE] -> {% data variables.product.product_name %} supported identity providers for SCIM are Entra ID, Okta, and OneLogin. For more information about SCIM, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations). +> {% data variables.product.github %}'s supported identity providers for SCIM are Entra ID, Okta, and OneLogin. For more information about SCIM, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations). > > {% data reusables.scim.enterprise-account-scim %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md index 23f1e16bbf0c..22aedfb2080f 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -1,6 +1,6 @@ --- title: Downloading your organization's SAML single sign-on recovery codes -intro: 'Organization owners should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.' +intro: 'Organization owners should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.github %} even if the identity provider for the organization is unavailable.' redirect_from: - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes @@ -23,9 +23,9 @@ Recovery codes should not be shared or distributed. We recommend saving them wit 1. To save your recovery codes, click **Download**, **Print**, or **Copy**. > [!NOTE] - > Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated. + > Your recovery codes will help get you back into {% data variables.product.github %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated. -1. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on. +1. Once you use a recovery code to regain access to {% data variables.product.github %}, it cannot be reused. Access will only be available for 24 hours before you'll be asked to sign in using single sign-on. ## Further reading diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 1e8e37799ff7..e9826e2255d7 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -1,6 +1,6 @@ --- title: Managing team synchronization for your organization -intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.' +intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.github %}.' redirect_from: - /articles/synchronizing-teams-between-your-identity-provider-and-github - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github @@ -19,7 +19,7 @@ shortTitle: Manage team synchronization ## About team synchronization -You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. +You can enable team synchronization between your IdP and {% data variables.product.github %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. {% data reusables.identity-and-permissions.about-team-sync %} diff --git a/content/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles.md b/content/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles.md index 0b62b9a0eaed..abbc3de63fd3 100644 --- a/content/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles.md +++ b/content/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles.md @@ -16,7 +16,7 @@ redirect_from: ## About custom repository roles -To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. +To perform any actions on {% data variables.product.github %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization). diff --git a/content/organizations/organizing-members-into-teams/about-teams.md b/content/organizations/organizing-members-into-teams/about-teams.md index 43d312fa94cd..31470a6b56c9 100644 --- a/content/organizations/organizing-members-into-teams/about-teams.md +++ b/content/organizations/organizing-members-into-teams/about-teams.md @@ -52,7 +52,7 @@ Organization members can create and participate in discussions with the team. Fo ## Nested teams -You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. +You can reflect your group or company's hierarchy within your {% data variables.product.github %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people. diff --git a/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index e183fe270183..b7957cdfc8cd 100644 --- a/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -1,9 +1,9 @@ --- title: Synchronizing a team with an identity provider group -intro: 'You can synchronize a {% data variables.product.product_name %} team with a supported identity provider (IdP) group to automatically add and remove team members.' +intro: 'You can synchronize a {% data variables.product.github %} team with a supported identity provider (IdP) group to automatically add and remove team members.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group -permissions: 'Organization owners can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' +permissions: 'Organization owners can synchronize a {% data variables.product.github %} team with an IdP group.' versions: ghec: '*' ghes: '*' @@ -19,11 +19,11 @@ shortTitle: Synchronize with an IdP {% data reusables.identity-and-permissions.about-team-sync %} {% ifversion ghec %}For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization) and [AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise).{% endif %} -{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. +{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.github %} team.{% endif %} You can assign an IdP group to multiple {% data variables.product.github %} teams. {% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} -Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}. +Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.github %}{% ifversion ghec %} or using the API{% endif %}. {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} @@ -32,13 +32,13 @@ Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP {% endif %} {% ifversion ghec %} -All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Team synchronization will fetch group information from your IdP at least once every hour, and reflect any changes in IdP group membership into {% data variables.product.product_name %}. +All team membership changes made through your IdP will appear in the audit log on {% data variables.product.github %} as changes made by the team synchronization bot. Team synchronization will fetch group information from your IdP at least once every hour, and reflect any changes in IdP group membership into {% data variables.product.github %}. Connecting a team to an IdP group may remove some team members. For more information, see [Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams). {% endif %} Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams#nested-teams), [AUTOTITLE](/organizations/organizing-members-into-teams/creating-a-team), and [AUTOTITLE](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy). -To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository). +To manage repository access for any {% data variables.product.github %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.github %}. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository). {% ifversion ghec %}You can also manage team synchronization with the API. For more information, see [AUTOTITLE](/rest/teams/team-sync).{% endif %} @@ -46,15 +46,15 @@ To manage repository access for any {% data variables.product.prodname_dotcom %} ## Requirements for members of synchronized teams -After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if: +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.github %} only if: {%- ifversion team-sync-manage-org-invites %} -* If team synchronization is not allowed to invite non-members to your organization, the person is already a member of the organization on {% data variables.product.product_name %}. +* If team synchronization is not allowed to invite non-members to your organization, the person is already a member of the organization on {% data variables.product.github %}. {%- endif %} -* The person has already logged in with their personal account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +* The person has already logged in with their personal account on {% data variables.product.github %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. * The person's SSO identity is a member of the IdP group. -Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from any teams mapped to IdP groups. For more information, see [AUTOTITLE](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity) and [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity). +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.github %} and lose access to repositories. Revoking a user's linked identity will also remove the user from any teams mapped to IdP groups. For more information, see [AUTOTITLE](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity) and [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity). A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group. @@ -67,7 +67,7 @@ To avoid unintentionally removing team members, we recommend enforcing SAML SSO {% data reusables.identity-and-permissions.team-and-idp-group %} {% ifversion ghec %} -Before you can connect a {% data variables.product.product_name %} team with an IdP group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization) and [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise). +Before you can connect a {% data variables.product.github %} team with an IdP group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization) and [AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise). To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. @@ -81,7 +81,7 @@ You must configure user provisioning with SCIM for {% data variables.location.pr ## Connecting an IdP group to a team -When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. +When you connect an IdP group to a {% data variables.product.github %} team, all users in the group are automatically added to the team. {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} From 80753fb30434cc5a177cf5189bb764a61abc8140 Mon Sep 17 00:00:00 2001 From: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Date: Tue, 21 Jan 2025 09:50:15 +0000 Subject: [PATCH 4/5] Remove `product_name` from `repositories` directory (#54016) --- ...ut-archiving-content-and-data-on-github.md | 6 ++--- .../archiving-a-github-repository/index.md | 2 +- .../referencing-and-citing-content.md | 2 +- .../managing-a-merge-queue.md | 8 +++--- .../renaming-a-branch.md | 2 +- .../viewing-branches-in-your-repository.md | 2 +- .../about-protected-branches.md | 4 +-- .../available-rules-for-rulesets.md | 2 +- .../about-repositories.md | 2 +- .../creating-a-new-repository.md | 2 +- .../creating-an-issues-only-repository.md | 2 +- .../index.md | 2 +- .../quickstart-for-repositories.md | 4 +-- .../repository-limits.md | 4 +-- .../troubleshooting-cloning-errors.md | 4 +-- .../about-readmes.md | 4 +-- .../about-repository-languages.md | 4 +-- ...classifying-your-repository-with-topics.md | 6 ++--- .../licensing-a-repository.md | 4 +-- ...fications-for-pushes-to-your-repository.md | 4 +-- ...-objects-in-archives-of-your-repository.md | 6 ++--- ...mmit-signoff-policy-for-your-repository.md | 2 +- .../setting-repository-visibility.md | 8 +++--- .../about-releases.md | 2 +- .../managing-releases-in-a-repository.md | 4 +-- .../viewing-a-projects-contributors.md | 4 +-- ...deployment-activity-for-your-repository.md | 2 +- .../viewing-traffic-to-a-repository.md | 2 +- .../adding-a-file-to-a-repository.md | 10 +++---- .../managing-files/creating-new-files.md | 6 ++--- .../deleting-files-in-a-repository.md | 4 +-- .../managing-files/editing-files.md | 4 +-- .../managing-files/index.md | 2 +- .../moving-a-file-to-a-new-location.md | 6 ++--- .../managing-files/renaming-a-file.md | 6 ++--- .../about-git-large-file-storage.md | 4 +-- .../about-large-files-on-github.md | 10 +++---- .../about-storage-and-bandwidth-usage.md | 2 +- ...llaboration-with-git-large-file-storage.md | 2 +- .../configuring-git-large-file-storage.md | 6 ++--- .../getting-permanent-links-to-files.md | 2 +- .../using-files/navigating-code-on-github.md | 2 +- .../working-with-non-code-files.md | 26 +++++++++---------- 43 files changed, 96 insertions(+), 96 deletions(-) diff --git a/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md b/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md index 5cc1c3b26fc2..937700ff8c9f 100644 --- a/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md +++ b/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md @@ -1,6 +1,6 @@ --- title: About archiving content and data on GitHub -intro: 'You can archive content and data on {% data variables.product.product_name %} for other people to view and reference.' +intro: 'You can archive content and data for other people to view and reference.' redirect_from: - /articles/about-archiving-content-and-data-on-github - /github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github @@ -14,7 +14,7 @@ shortTitle: Archive content & data --- ## Persistence of public repositories -{% data variables.product.product_name %} intends to keep your public repositories available unless you remove them. In some cases, we may make public content unavailable, for example if: +{% data variables.product.company_short %} intends to keep your public repositories available unless you remove them. In some cases, we may make public content unavailable, for example if: * We receive a [DMCA Takedown Notice](/free-pro-team@latest/site-policy/content-removal-policies/dmca-takedown-policy) for content in a repository. * We determine that a repository's content violates our [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines) or [Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service). @@ -33,4 +33,4 @@ You can opt out of the {% data variables.product.prodname_archive %} for your re ## Adding an open source license to increase archivability -Libraries and researchers may require legal protections to create archives of publicly available content. If you want third parties to consider your work on {% data variables.product.product_name %} for archiving, you can add an [open source license](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository) to your projects. An open source license gives contributors explicit permissions to copy and distribute the material in your repositories. +Libraries and researchers may require legal protections to create archives of publicly available content. If you want third parties to consider your work on {% data variables.product.github %} for archiving, you can add an [open source license](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository) to your projects. An open source license gives contributors explicit permissions to copy and distribute the material in your repositories. diff --git a/content/repositories/archiving-a-github-repository/index.md b/content/repositories/archiving-a-github-repository/index.md index 41db1087a1ed..ec0d79231451 100644 --- a/content/repositories/archiving-a-github-repository/index.md +++ b/content/repositories/archiving-a-github-repository/index.md @@ -1,6 +1,6 @@ --- title: Archiving a GitHub repository -intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.' +intro: 'You can archive, back up, and cite your work using the {% data variables.product.github %} UI, the API, or third-party tools and services.' redirect_from: - /articles/can-i-archive-a-repository - /articles/archiving-a-github-repository diff --git a/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md b/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md index d6ad6cce4079..22beb97d461b 100644 --- a/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md +++ b/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md @@ -27,7 +27,7 @@ To make your repositories easier to reference in academic literature, you can cr 1. Navigate to the [Zenodo {% data variables.product.prodname_dotcom %} page](https://zenodo.org/account/settings/github/). 1. To the right of the name of the repository you want to archive, toggle the button to **On**. -Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.product_name %} [release](/repositories/releasing-projects-on-github/about-releases). Follow the steps at [AUTOTITLE](/repositories/releasing-projects-on-github/managing-releases-in-a-repository) to create a new one. +Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.github %} [release](/repositories/releasing-projects-on-github/about-releases). Follow the steps at [AUTOTITLE](/repositories/releasing-projects-on-github/managing-releases-in-a-repository) to create a new one. ## Publicizing and citing research material with Figshare diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md index 6a2b0057e967..a6f7f2af6667 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md @@ -80,7 +80,7 @@ Once you have enabled the "Require merge queue" setting, you can also access the As pull requests are added to the merge queue, the merge queue ensures that they are merged in a first-in-first-out order where the required checks are always satisfied. -A merge queue creates temporary branches with a special prefix to validate pull request changes. When a pull request is added to the merge queue, the changes in the pull request are grouped into a `merge_group` with the latest version of the `base_branch` as well as changes from pull requests ahead of it in the queue. {% data variables.product.product_name %} will merge all these changes into the `base_branch` once the checks required by the branch protections of `base_branch` pass. +A merge queue creates temporary branches with a special prefix to validate pull request changes. When a pull request is added to the merge queue, the changes in the pull request are grouped into a `merge_group` with the latest version of the `base_branch` as well as changes from pull requests ahead of it in the queue. {% data variables.product.github %} will merge all these changes into the `base_branch` once the checks required by the branch protections of `base_branch` pass. For information about merge methods, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges). @@ -92,7 +92,7 @@ When multiple pull requests are added to the merge queue and when the temporary 1. The merge queue creates a temporary branch with the prefix of `main/pr-1` that contains code changes from the target branch and pull request #1. A `merge_group` webhook event of type `checks_requested` is dispatched and the merge queue will await a response from your CI provider. 1. User adds pull request #2 to the merge queue. 1. The merge queue creates a temporary branch with the prefix of `main/pr-2` that contains code changes from the target branch, pull request #1, and pull request #2, and dispatches webhooks. -1. When the {% data variables.product.product_name %} API receives successful CI responses for `merge_group` branches `main/pr-1` and `main/pr-2`, the temporary branch `main/pr-2` will be merged in to the target branch. The target branch now contains both changes from pull request #1 and #2. +1. When the {% data variables.product.github %} API receives successful CI responses for `merge_group` branches `main/pr-1` and `main/pr-2`, the temporary branch `main/pr-2` will be merged in to the target branch. The target branch now contains both changes from pull request #1 and #2. ### Failing CI @@ -104,9 +104,9 @@ The following scenario outlines what happens when a CI reports a failing status 1. The merge queue creates a temporary branch with the prefix of `main/pr-1` that contains code changes from the target branch and pull request #1. A `merge_group` webhook event of type `checks_requested` is dispatched and the merge queue will await a response from your CI provider. 1. User adds pull request #2 to the merge queue. 1. The merge queue creates a temporary branch with the prefix of `main/pr-2` that contains code changes from the target branch, pull request #1, and pull request #2, and dispatches webhooks. -1. When the {% data variables.product.product_name %} API receives a failing status for `main/pr-1`, the merge queue automatically removes pull request #1 from the merge queue. +1. When the {% data variables.product.github %} API receives a failing status for `main/pr-1`, the merge queue automatically removes pull request #1 from the merge queue. 1. The merge queue recreates the temporary branch with the prefix of `main/pr-2` to only contain changes from the target branch and pull request #2. -1. When the {% data variables.product.product_name %} API receives successful CI responses for `merge_group` branch `main/pr-2`, the temporary branch `main/pr-2` will be merged in to the target branch without pull request #1 included. +1. When the {% data variables.product.github %} API receives successful CI responses for `merge_group` branch `main/pr-2`, the temporary branch `main/pr-2` will be merged in to the target branch without pull request #1 included. {% data reusables.pull_requests.merge-queue-removal-reasons %} diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index adc8dae02eef..b5d87b7f5802 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -36,7 +36,7 @@ Organizational rulesets that apply to branches of a repository will no longer al ## Updating a local clone after a branch name changes -After you rename a branch in a repository on {% data variables.product.product_name %}, any collaborator with a local clone of the repository will need to update the clone. +After you rename a branch in a repository on {% data variables.product.github %}, any collaborator with a local clone of the repository will need to update the clone. From the local clone of the repository on a computer, run the following commands to update the name of the default branch. diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md index d76b9e37918a..68de15dedb63 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md @@ -1,6 +1,6 @@ --- title: Viewing branches in your repository -intro: 'Branches are central to collaboration on {% data variables.product.product_name %}, and the best way to view them is the branches page.' +intro: 'Branches are central to collaboration on {% data variables.product.github %}, and the best way to view them is the branches page.' redirect_from: - /articles/viewing-branches-in-your-repository - /github/administering-a-repository/viewing-branches-in-your-repository diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md index 5064e5190ddf..af2abeb38f33 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md @@ -129,7 +129,7 @@ When you enable required commit signing on a branch, contributors {% ifversion f > If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. {% endif %} -You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally). +You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request. However, you cannot squash and merge a pull request into the branch on {% data variables.product.github %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.github %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally). {% ifversion fpt or ghec %} For more information about merge methods, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github).{% endif %} @@ -180,7 +180,7 @@ You can only give push access to a protected branch, or give permission to creat ### Allow force pushes -By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push: +By default, {% data variables.product.github %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push: 1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions. 1. Allow only specific people or teams to force push to the branch. diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md index 71bd27fbc811..83ef2603b480 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md @@ -96,7 +96,7 @@ With both methods, we use the `verified_signature?` to confirm if a commit has a {% endif %} -You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally). +You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request. However, you cannot squash and merge a pull request into the branch on {% data variables.product.github %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.github %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally). {% ifversion fpt or ghec %} For more information about merge methods, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github).{% endif %} diff --git a/content/repositories/creating-and-managing-repositories/about-repositories.md b/content/repositories/creating-and-managing-repositories/about-repositories.md index c3ff3a39562b..37d350e09ce5 100644 --- a/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -38,7 +38,7 @@ Clone | To download a full copy of a repository's data from {% data variables.lo Fork | A new repository that shares code and visibility settings with the original "upstream" repository. Merge | To take the changes from one branch and apply them to another. Pull request | A request to merge changes from one branch into another. -Remote | A repository stored on {% data variables.product.product_name %}, not on your computer. +Remote | A repository stored on {% data variables.product.github %}, not on your computer. Upstream | The branch on an original repository that has been forked or cloned. The corresponding branch on the cloned or forked repository is called the "downstream." {% endrowheaders %} diff --git a/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index d38f35074398..a5c1f9772baf 100644 --- a/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -37,7 +37,7 @@ topics: {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} -1. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line), [AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts). +1. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.github %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line), [AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts). * You can create a README, which is a document describing your project. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes). * You can create a _.gitignore_ file, which is a set of ignore rules. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/ignoring-files).{% ifversion fpt or ghec %} * You can choose to add a software license for your project. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository).{% endif %} diff --git a/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md index 118051820eab..ac6fe17a1b83 100644 --- a/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md +++ b/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md @@ -1,6 +1,6 @@ --- title: Creating an issues-only repository -intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.' +intro: '{% data variables.product.github %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.' redirect_from: - /articles/issues-only-access-permissions - /articles/is-there-issues-only-access-to-organization-repositories diff --git a/content/repositories/creating-and-managing-repositories/index.md b/content/repositories/creating-and-managing-repositories/index.md index 1b7fb089aa3b..6b02abb5e163 100644 --- a/content/repositories/creating-and-managing-repositories/index.md +++ b/content/repositories/creating-and-managing-repositories/index.md @@ -1,6 +1,6 @@ --- title: Creating and managing repositories -intro: 'You can create a repository on {% data variables.product.product_name %} to store and collaborate on your project''s files, then manage the repository''s name and location.' +intro: 'You can create a repository on {% data variables.product.github %} to store and collaborate on your project''s files, then manage the repository''s name and location.' redirect_from: - /articles/creating-a-repository-on-github - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github diff --git a/content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md b/content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md index 67a9387fab06..b1479d57e097 100644 --- a/content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md +++ b/content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md @@ -20,7 +20,7 @@ topics: --- ## Create a repository -{% data variables.product.product_name %} repositories store a variety of projects. In this guide, you'll create a repository and commit your first change. +{% data variables.product.github %} repositories store a variety of projects. In this guide, you'll create a repository and commit your first change. {% webui %} @@ -28,7 +28,7 @@ topics: 1. Type a short, memorable name for your repository. For example, "hello-world". ![Screenshot of the first step in creating a repository. The "Repository name" field contains the text "hello-world" and is outlined in dark orange.](/assets/images/help/repository/create-repository-name.png) -1. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}." +1. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.github %}." {% data reusables.repositories.choose-repo-visibility %} {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} diff --git a/content/repositories/creating-and-managing-repositories/repository-limits.md b/content/repositories/creating-and-managing-repositories/repository-limits.md index 3edb8b5460b5..81a839ccab87 100644 --- a/content/repositories/creating-and-managing-repositories/repository-limits.md +++ b/content/repositories/creating-and-managing-repositories/repository-limits.md @@ -9,9 +9,9 @@ topics: - Repositories --- -Certain types of repository resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time. +Certain types of repository resources can be quite large, requiring excessive processing on {% data variables.product.github %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time. -Most of the limits below affect both {% data variables.product.product_name %} and the API. +Most of the limits below affect both {% data variables.product.github %} and the API. ## Text limits diff --git a/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md index 7e06a71eb071..854c171f1839 100644 --- a/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md +++ b/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md @@ -45,7 +45,7 @@ Here's an example of an HTTPS error you might receive: ### Check your Git version -There's no minimum Git version necessary to interact with {% data variables.product.product_name %}, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always [download the latest version on the Git website](https://git-scm.com/downloads). +There's no minimum Git version necessary to interact with {% data variables.product.github %}, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always [download the latest version on the Git website](https://git-scm.com/downloads). ### Ensure the remote is correct @@ -115,7 +115,7 @@ Make sure that you have access to the repository in one of these ways: In rare circumstances, you may not have the proper SSH access to a repository. -You should ensure that the SSH key you are using is attached to your personal account on {% data variables.product.product_name %}. You can check this by typing +You should ensure that the SSH key you are using is attached to your personal account on {% data variables.product.github %}. You can check this by typing the following into the command line: ```shell diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index 2c709fc72edc..825b4b96d414 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -27,7 +27,7 @@ A README is often the first item a visitor will see when visiting your repositor * Where users can get help with your project * Who maintains and contributes to the project -If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors. +If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.github %} will recognize and automatically surface your README to repository visitors. If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory. @@ -37,7 +37,7 @@ When your README is viewed on GitHub, any content beyond 500 KiB will be truncat ## Auto-generated table of contents for README files -For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="Table of Contents" %} menu icon at the top left of the rendered page. +For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.github %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="Table of Contents" %} menu icon at the top left of the rendered page. ![Screenshot of the README for a repository. In the upper-left corner, the "Table of contents" dropdown menu (list icon) is expanded.](/assets/images/help/repository/readme-automatic-toc.png) diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md index 9e7192ce5f03..31d6b6620b3e 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md @@ -18,11 +18,11 @@ topics: - Repositories shortTitle: Repository languages --- -{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github-linguist/linguist) to +{% data variables.product.github %} uses the open source [Linguist library](https://github.com/github-linguist/linguist) to determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch. Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github-linguist/linguist/blob/main/docs/troubleshooting.md) for help. Note that Linguist only works for repositories with fewer than 100,000 files. ## Markup languages -Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.product_name %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new). +Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.github %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new). diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index 10024e3be955..acfb98592f8d 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -23,13 +23,13 @@ With topics, you can explore repositories in a particular subject area, find pro To browse the most used topics, go to {% data variables.product.product_url %}/topics/. -{% ifversion fpt or ghec %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %} +{% ifversion fpt or ghec %}You can contribute to {% data variables.product.github %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %} -Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %} +Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.github %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %} {% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results. -You can search for repositories that are associated with a particular topic. For more information, see [AUTOTITLE](/search-github/searching-on-github/searching-for-repositories#search-by-topic). You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see [AUTOTITLE](/search-github/searching-on-github/searching-topics). +You can search for repositories that are associated with a particular topic. For more information, see [AUTOTITLE](/search-github/searching-on-github/searching-for-repositories#search-by-topic). You can also search for a list of topics on {% data variables.product.github %}. For more information, see [AUTOTITLE](/search-github/searching-on-github/searching-topics). When creating a topic: * Use lowercase letters, numbers, and hyphens. diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 19cb3d345a41..0c94df4a3c40 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -20,7 +20,7 @@ We created [choosealicense.com](https://choosealicense.com), to help you underst You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project. > [!NOTE] -> If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service), {% endif %}other users of {% data variables.location.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility). +> If you publish your source code in a public repository on {% data variables.product.github %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service), {% endif %}other users of {% data variables.location.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility). ## Determining the location of your license @@ -77,7 +77,7 @@ When you search by a family license, your results will include all licenses in t ## Detecting a license -[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's _LICENSE_ file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's _LICENSE_ file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/licenses) and [gives us insight into how repositories on {% data variables.product.github %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your _LICENSE_ file and note the complexity somewhere else, such as your repository's _README_ file. diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 8b4e8eb3c6ca..823a8b94a0cc 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -23,7 +23,7 @@ Each email notification for a push to a repository lists the new commits and lin * The name of the repository where the commit was made * The branch a commit was made in -* The SHA1 of the commit, including a link to the diff in {% data variables.product.product_name %} +* The SHA1 of the commit, including a link to the diff in {% data variables.product.github %} * The author of the commit * The date when the commit was made * The files that were changed as part of the commit @@ -43,7 +43,7 @@ You can filter email notifications you receive for pushes to a repository. For m {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 1. In the "Address" field, type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address. -1. If you operate your own server, you can verify the integrity of emails via the "Approved header." The "Approved header" is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}. +1. If you operate your own server, you can verify the integrity of emails via the "Approved header." The "Approved header" is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.github %}. 1. Click **Setup notifications**. ## Further reading diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md index 790ce9b79e68..15732cc28bf0 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -1,7 +1,7 @@ --- title: Managing Git LFS objects in archives of your repository shortTitle: 'Managing {% data variables.large_files.product_name_short %} objects in archives' -intro: 'You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives, such as ZIP files and tarballs, {% data variables.product.product_name %} creates for your repository.' +intro: 'You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives created for your repository.' permissions: 'People with admin permissions for a repository can manage whether {% data variables.large_files.product_name_short %} objects are included in archives of the repository.' versions: fpt: '*' @@ -14,11 +14,11 @@ redirect_from: --- ## About {% data variables.large_files.product_name_short %} objects in archives -{% data variables.product.product_name %} creates [source code archives](/repositories/working-with-files/using-files/downloading-source-code-archives) of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, {% data variables.large_files.product_name_short %} objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the {% data variables.large_files.product_name_short %} objects instead. To be included, the {% data variables.large_files.product_name_short %} objects must be covered by tracking rules in a _.gitattributes_ file that has been committed to the repository. +{% data variables.product.github %} creates [source code archives](/repositories/working-with-files/using-files/downloading-source-code-archives) of your repository in the form of ZIP files and tarballs. People can download these archives on the main page of your repository or as release assets. By default, {% data variables.large_files.product_name_short %} objects are not included in these archives, only the pointer files to these objects. To improve the usability of archives for your repository, you can choose to include the {% data variables.large_files.product_name_short %} objects instead. To be included, the {% data variables.large_files.product_name_short %} objects must be covered by tracking rules in a _.gitattributes_ file that has been committed to the repository. If you choose to include {% data variables.large_files.product_name_short %} objects in archives of your repository, every download of those archives will count towards bandwidth usage for your account. Each account receives {% data variables.large_files.initial_bandwidth_quota %} per month of bandwidth for free, and you can pay for additional usage. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage) and [AUTOTITLE](/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage). -If you use an external LFS server (configured in your _.lfsconfig_), those LFS files will not be included in archives of the repository. The archive will only contain files that have been committed to {% data variables.product.product_name %}. +If you use an external LFS server (configured in your _.lfsconfig_), those LFS files will not be included in archives of the repository. The archive will only contain files that have been committed to {% data variables.product.github %}. ## Managing {% data variables.large_files.product_name_short %} objects in archives diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md index 79b580e4bcc9..ec692d7bf812 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md @@ -1,6 +1,6 @@ --- title: Managing the commit signoff policy for your repository -intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.' +intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.github %}''s web interface.' versions: fpt: '*' ghec: '*' diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 05046c49d357..1faeea9f7623 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -42,9 +42,9 @@ We recommend reviewing the following caveats before you change the visibility of ### Making a repository private -* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private. +* {% data variables.product.github %} will detach public forks of the public repository and put them into a new network. Public forks are not made private. {%- ifversion ghes or ghec %} -* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. The visibility of any forks will also change to private. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility) +* If you change a repository's visibility from internal to private, {% data variables.product.github %} will remove forks that belong to any user without access to the newly private repository. The visibility of any forks will also change to private. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility) {%- endif %} {%- ifversion fpt %} * If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans) and [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site). @@ -61,13 +61,13 @@ We recommend reviewing the following caveats before you change the visibility of ### Making a repository internal -* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility) +* Any forks of the repository will remain in the repository network, and {% data variables.product.github %} maintains the relationship between the root repository and the fork. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility) {% endif %} ### Making a repository public -* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository){% ifversion fpt or ghec %} +* {% data variables.product.github %} will detach private forks and turn them into a standalone private repository. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository){% ifversion fpt or ghec %} * If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see [AUTOTITLE](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories). * The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. * Actions history and logs will be visible to everyone. If your repository had reusable or required workflows that were shared from a different repository in your organization, the workflow file path including the repository name will be visible in the logs. For more information on how to remove workflow runs and artifacts see [AUTOTITLE](/actions/managing-workflow-runs#deleting-logs) and [AUTOTITLE](/rest/actions/workflow-runs). diff --git a/content/repositories/releasing-projects-on-github/about-releases.md b/content/repositories/releasing-projects-on-github/about-releases.md index 755b50014610..047ed11b7b6b 100644 --- a/content/repositories/releasing-projects-on-github/about-releases.md +++ b/content/repositories/releasing-projects-on-github/about-releases.md @@ -33,7 +33,7 @@ When viewing the details for a release, the creation date for each release asset GitHub will automatically include links to download a zip file and a tarball containing the contents of the repository at the point of the tag's creation. {% ifversion fpt or ghec %} -People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository). +People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.github %} creates for each release. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository). If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories). diff --git a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index 95031ca26d28..74311dfa2b63 100644 --- a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -26,7 +26,7 @@ You can create new releases with release notes, @mentions of contributors, and l {% ifversion fpt or ghec %} You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see [AUTOTITLE](/actions/creating-actions/publishing-actions-in-github-marketplace). -You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository). +You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.github %} creates for each release. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository). {% endif %} ## Creating a release @@ -61,7 +61,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a {% data variables.release-phases.public_preview %} release" --prerelease ``` -If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users. +If you @mention any {% data variables.product.github %} users in the notes, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {% endcli %} diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md index 75582205fd8e..c7e5a8db5966 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md @@ -43,11 +43,11 @@ You can also see a list of people who have contributed to the project's Python d If you don't appear in a repository's contributors graph, it may be because: * You aren't one of the top 100 contributors. * Your commits haven't been merged into the default branch. -* The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}. +* The email address you used to author the commits isn't connected to your {% data variables.product.github %} account. > [!TIP] > To list all commit contributors in a repository, see [AUTOTITLE](/rest/repos/repos#list-repository-contributors). If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address) and [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account). +If the email address you used to author the commits is not connected to your {% data variables.product.github %} account, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address) and [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account). diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md index 9e38be6888a6..40a2a3626567 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md @@ -17,7 +17,7 @@ shortTitle: View deployment activity > [!NOTE] > The deployments dashboard is currently in {% data variables.release-phases.public_preview %} and subject to change. -People with read access to a repository can see an overview of all current deployments and a log of past deployment activity, if the repository's deployment workflow is integrated with {% data variables.product.product_name %} through the Deployments API or an app from [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment). For more information, see [AUTOTITLE](/rest/repos#deployments). +People with read access to a repository can see an overview of all current deployments and a log of past deployment activity, if the repository's deployment workflow is integrated with {% data variables.product.github %} through the Deployments API or an app from [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment). For more information, see [AUTOTITLE](/rest/repos#deployments). You can also see deployment information on the "Conversation" tab of a pull request. diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md index 7e7d647adc1b..b533de17ef28 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md @@ -14,7 +14,7 @@ topics: shortTitle: View repository traffic --- -You can navigate to referring sites, excluding search engines and {% data variables.product.product_name %} itself, from the links the specific paths were referred from. The popular content links to the specific content that generated traffic. +You can navigate to referring sites, excluding search engines and {% data variables.product.github %} itself, from the links the specific paths were referred from. The popular content links to the specific content that generated traffic. Referring sites and popular content are ordered by views and unique visitors. Full clones and visitor information update hourly, while referring sites and popular content sections update daily. All data in the traffic graph uses the UTC+0 timezone, regardless of your location. diff --git a/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md b/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md index 6c61310516f1..34bc9f087f6b 100644 --- a/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md +++ b/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md @@ -1,6 +1,6 @@ --- title: Adding a file to a repository -intro: 'You can upload and commit an existing file to a repository on {% data variables.product.product_name %} or by using the command line.' +intro: 'You can upload and commit an existing file to a repository on {% data variables.product.github %} or by using the command line.' redirect_from: - /articles/adding-a-file-to-a-repository - /github/managing-files-in-a-repository/adding-a-file-to-a-repository @@ -19,11 +19,11 @@ topics: shortTitle: Add a file --- -## Adding a file to a repository on {% data variables.product.product_name %} +## Adding a file to a repository on {% data variables.product.github %} Files that you add to a repository via a browser are limited to {% data variables.large_files.max_github_browser_size %} per file. You can add larger files, up to {% data variables.large_files.max_github_size %} each, via the command line. For more information, see [Adding a file to a repository using the command line](#adding-a-file-to-a-repository-using-the-command-line). To add files larger than {% data variables.large_files.max_github_size %}, you must use {% data variables.large_files.product_name_long %}. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github). -You can upload multiple files to {% data variables.product.product_name %} at the same time. +You can upload multiple files to {% data variables.product.github %} at the same time. {% data reusables.repositories.protected-branches-block-web-edits-uploads %} @@ -55,13 +55,13 @@ Your repository may be secured by push protection. With push protection, {% data You can upload an existing file to a repository on {% data variables.product.prodname_dotcom %} using the command line. > [!TIP] -> You can also [add an existing file to a repository from the {% data variables.product.product_name %} website](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository). +> You can also [add an existing file to a repository from the {% data variables.product.github %} website](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository). {% data reusables.command_line.manipulating_file_prereqs %} {% data reusables.repositories.sensitive-info-warning %} -1. On your computer, move the file you'd like to upload to {% data variables.product.product_name %} into the local directory that was created when you cloned the repository. +1. On your computer, move the file you'd like to upload to {% data variables.product.github %} into the local directory that was created when you cloned the repository. {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} {% data reusables.git.stage_for_commit %} diff --git a/content/repositories/working-with-files/managing-files/creating-new-files.md b/content/repositories/working-with-files/managing-files/creating-new-files.md index 9c8a29c9f899..940e828a4f94 100644 --- a/content/repositories/working-with-files/managing-files/creating-new-files.md +++ b/content/repositories/working-with-files/managing-files/creating-new-files.md @@ -1,6 +1,6 @@ --- title: Creating new files -intro: 'You can create new files directly on {% data variables.product.product_name %} in any repository you have write access to.' +intro: 'You can create new files directly on {% data variables.product.github %} in any repository you have write access to.' redirect_from: - /articles/creating-new-files - /github/managing-files-in-a-repository/creating-new-files @@ -12,10 +12,10 @@ versions: topics: - Repositories --- -When creating a file on {% data variables.product.product_name %}, consider the following: +When creating a file on {% data variables.product.github %}, consider the following: * If you try to create a new file in a repository that you don’t have access to, we will fork the project to your personal account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. -* File names created via the web interface can only contain alphanumeric characters and hyphens (`-`). To use other characters, [create and commit the files locally, then push them to the repository on {% data variables.product.product_name %}](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository). +* File names created via the web interface can only contain alphanumeric characters and hyphens (`-`). To use other characters, [create and commit the files locally, then push them to the repository on {% data variables.product.github %}](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository). {%- ifversion push-rulesets %} * {% data reusables.repositories.rulesets-push-rules-general-info-for-related-articles %} {% endif %} diff --git a/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md b/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md index 0176b89da95e..dc138c6a387f 100644 --- a/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md +++ b/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md @@ -1,6 +1,6 @@ --- title: Deleting files in a repository -intro: 'You can delete an individual file or an entire directory in your repository on {% data variables.product.product_name %}.' +intro: 'You can delete an individual file or an entire directory in your repository on {% data variables.product.github %}.' redirect_from: - /articles/deleting-files - /github/managing-files-in-a-repository/deleting-files @@ -22,7 +22,7 @@ You can delete an individual file in your repository or an entire directory, inc If you try to delete a file or directory in a repository that you don’t have write permissions to, we'll fork the project to your personal account and help you send a pull request to the original repository after you commit your change. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -If the file or directory you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.product_name %}, you must remove the file from your repository's history. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository). +If the file or directory you deleted contains sensitive data, the data will still be available in the repository's Git history. To completely remove the file from {% data variables.product.github %}, you must remove the file from your repository's history. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository). ## Deleting a file diff --git a/content/repositories/working-with-files/managing-files/editing-files.md b/content/repositories/working-with-files/managing-files/editing-files.md index 778d61534609..f40f8448ee9e 100644 --- a/content/repositories/working-with-files/managing-files/editing-files.md +++ b/content/repositories/working-with-files/managing-files/editing-files.md @@ -1,6 +1,6 @@ --- title: Editing files -intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.' +intro: 'You can edit files directly on {% data variables.product.github %} in any of your repositories using the file editor.' redirect_from: - /articles/editing-files - /articles/editing-files-in-your-repository @@ -24,7 +24,7 @@ shortTitle: Edit files > {% data reusables.repositories.protected-branches-block-web-edits-uploads %} > [!NOTE] -> {% data variables.product.product_name %}'s file editor uses [CodeMirror](https://codemirror.net/). +> {% data variables.product.github %}'s file editor uses [CodeMirror](https://codemirror.net/). 1. In your repository, browse to the file you want to edit. {% data reusables.repositories.edit-file %} diff --git a/content/repositories/working-with-files/managing-files/index.md b/content/repositories/working-with-files/managing-files/index.md index 97fa660d3bb0..077a041aef1f 100644 --- a/content/repositories/working-with-files/managing-files/index.md +++ b/content/repositories/working-with-files/managing-files/index.md @@ -1,6 +1,6 @@ --- title: Managing files -intro: 'You can create, edit, move, and delete files in a repository, directly on {% data variables.product.product_name %} or on the command line.' +intro: 'You can create, edit, move, and delete files in a repository, directly on {% data variables.product.github %} or on the command line.' redirect_from: - /articles/managing-files-on-github - /github/managing-files-in-a-repository/managing-files-on-github diff --git a/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md b/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md index 65b115b07e6c..d4ad351538b3 100644 --- a/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md +++ b/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md @@ -1,6 +1,6 @@ --- title: Moving a file to a new location -intro: 'You can move a file to a different directory on {% data variables.product.product_name %} or by using the command line.' +intro: 'You can move a file to a different directory on {% data variables.product.github %} or by using the command line.' redirect_from: - /articles/moving-a-file-to-a-new-location - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location @@ -18,7 +18,7 @@ shortTitle: Move a file --- In addition to changing the file location, you can also [update the contents of your file](/repositories/working-with-files/managing-files/editing-files), or [give it a new name](/repositories/working-with-files/managing-files/renaming-a-file) in the same commit. -## Moving a file to a new location on {% data variables.product.product_name %} +## Moving a file to a new location on {% data variables.product.github %} > [!TIP] > * If you try to move a file in a repository that you don’t have access to, we'll fork the project to your personal account and help you send [a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change. @@ -38,7 +38,7 @@ In addition to changing the file location, you can also [update the contents of You can use the command line to move files within a repository by removing the file from the old location and then adding it in the new location. -Many files can be [moved directly on {% data variables.product.product_name %}](/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location), but some files, such as images, require that you move them from the command line. +Many files can be [moved directly on {% data variables.product.github %}](/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location), but some files, such as images, require that you move them from the command line. {% data reusables.command_line.manipulating_file_prereqs %} diff --git a/content/repositories/working-with-files/managing-files/renaming-a-file.md b/content/repositories/working-with-files/managing-files/renaming-a-file.md index 1c0cf0a32114..41238823f446 100644 --- a/content/repositories/working-with-files/managing-files/renaming-a-file.md +++ b/content/repositories/working-with-files/managing-files/renaming-a-file.md @@ -1,6 +1,6 @@ --- title: Renaming a file -intro: 'You can rename any file in your repository directly in {% data variables.product.product_name %} or by using the command line.' +intro: 'You can rename any file in your repository directly in {% data variables.product.github %} or by using the command line.' redirect_from: - /articles/renaming-a-file - /github/managing-files-in-a-repository/renaming-a-file @@ -16,7 +16,7 @@ topics: - Repositories --- -## Renaming a file on {% data variables.product.product_name %} +## Renaming a file on {% data variables.product.github %} Renaming a file also gives you the opportunity to [move the file to a new location](/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location). @@ -37,7 +37,7 @@ Renaming a file also gives you the opportunity to [move the file to a new locati You can use the command line to rename any file in your repository. -Many files can be renamed directly on {% data variables.product.product_name %}, but some files, such as images, require that you rename them from the command line. +Many files can be renamed directly on {% data variables.product.github %}, but some files, such as images, require that you rename them from the command line. {% data reusables.command_line.manipulating_file_prereqs %} diff --git a/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index 22e5d3dce2af..5c15db375678 100644 --- a/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- title: About Git Large File Storage -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' +intro: '{% data variables.product.github %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' redirect_from: - /articles/about-large-file-storage - /articles/about-git-large-file-storage @@ -15,7 +15,7 @@ shortTitle: Git Large File Storage ## About {% data variables.large_files.product_name_long %} -{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you. +{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.github %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.github %} uses the pointer file as a map to go and find the large file for you. {% ifversion fpt or ghec %} Different maximum size limits for {% data variables.large_files.product_name_short %} apply depending on your {% data variables.product.prodname_dotcom %} plan. diff --git a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 2dd87b058800..9ce473e78917 100644 --- a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -1,6 +1,6 @@ --- title: About large files on GitHub -intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.' +intro: '{% data variables.product.github %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.' redirect_from: - /articles/distributing-large-binaries - /github/managing-large-files/distributing-large-binaries @@ -23,18 +23,18 @@ versions: shortTitle: Large files --- -## About size limits on {% data variables.product.product_name %} +## About size limits on {% data variables.product.github %} -{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file {% ifversion fpt or ghec %}and repository sizes{% else %} sizes and recommendations for repository sizes{% endif %}. {% ifversion fpt or ghec %}To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.{% endif %} +{% data variables.product.github %} tries to provide abundant storage for all Git repositories, although there are hard limits for file {% ifversion fpt or ghec %}and repository sizes{% else %} sizes and recommendations for repository sizes{% endif %}. {% ifversion fpt or ghec %}To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.{% endif %} ### File size limits -{% data variables.product.product_name %} limits the size of files allowed in repositories. If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see [Removing files from a repository's history](#removing-files-from-a-repositorys-history). +{% data variables.product.github %} limits the size of files allowed in repositories. If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see [Removing files from a repository's history](#removing-files-from-a-repositorys-history). > [!NOTE] > If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository). -{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise).{% endif %} +{% ifversion ghes %}By default, {% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.github %}{% endif %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise).{% endif %} To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-git-large-file-storage). diff --git a/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md index 0a54bbbe33cc..36969de57d82 100644 --- a/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md @@ -12,7 +12,7 @@ versions: ghec: '*' shortTitle: Storage & bandwidth --- -{% data variables.large_files.product_name_short %} is available for every repository on {% data variables.product.product_name %}, whether or not your account or organization has a paid subscription. +{% data variables.large_files.product_name_short %} is available for every repository on {% data variables.product.github %}, whether or not your account or organization has a paid subscription. ## Tracking storage and bandwidth use diff --git a/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md index 6eb0ab78c490..d272a12e397e 100644 --- a/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md @@ -19,7 +19,7 @@ If collaborators on your repository don't have {% data variables.large_files.pro ## Viewing large files in pull requests -{% data variables.product.product_name %} does not render some {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown, with contents similar to the following: +{% data variables.product.github %} does not render some {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown, with contents similar to the following: ```text +version https://git-lfs.github.com/spec/vi diff --git a/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md index 46a08ce608de..1ab3d42cf659 100644 --- a/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md +++ b/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md @@ -12,14 +12,14 @@ versions: ghec: '*' shortTitle: Configure Git LFS --- -If there are existing files in your repository that you'd like to use {% data variables.product.product_name %} with, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage). +If there are existing files in your repository that you'd like to use with {% data variables.product.github %}, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage). {% data reusables.large_files.resolving-upload-failures %} {% ifversion ghes %} > [!NOTE] -> Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see [AUTOTITLE](/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise). +> Before trying to push a large file to {% data variables.product.prodname_ghe_server %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see [AUTOTITLE](/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise). {% endif %} @@ -49,7 +49,7 @@ If there are existing files in your repository that you'd like to use {% data va git add path/to/file.psd ``` -1. Commit the file and push it to {% data variables.product.product_name %}: +1. Commit the file and push it to {% data variables.product.github %}: ```shell git commit -m "add file.psd" diff --git a/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md index 888b09ad4d20..415b89842715 100644 --- a/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md +++ b/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md @@ -17,7 +17,7 @@ shortTitle: Permanent links to files --- > [!TIP] -> Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts. +> Press "?" on any page in {% data variables.product.github %} to see all available keyboard shortcuts. ## File views show the latest version on a branch diff --git a/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/content/repositories/working-with-files/using-files/navigating-code-on-github.md index 259ca712e625..a129d1989a0a 100644 --- a/content/repositories/working-with-files/using-files/navigating-code-on-github.md +++ b/content/repositories/working-with-files/using-files/navigating-code-on-github.md @@ -1,6 +1,6 @@ --- title: Navigating code on GitHub -intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.' +intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.github %}.' redirect_from: - /articles/navigating-code-on-github - /github/managing-files-in-a-repository/navigating-code-on-github diff --git a/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/content/repositories/working-with-files/using-files/working-with-non-code-files.md index a61b1d9ef9b1..f46a8702174b 100644 --- a/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -1,6 +1,6 @@ --- title: Working with non-code files -intro: '{% data variables.product.product_name %} supports rendering and diffing in a number of non-code file formats.' +intro: '{% data variables.product.github %} supports rendering and diffing in a number of non-code file formats.' redirect_from: - /articles/rendering-and-diffing-images - /github/managing-files-in-a-repository/rendering-and-diffing-images @@ -36,7 +36,7 @@ shortTitle: Working with non-code files ## Rendering and diffing images -{% data variables.product.product_name %} can display several common image formats, including PNG, JPG, GIF, PSD, and SVG. In addition to simply displaying them, there are several ways to compare differences between versions of those image formats. +{% data variables.product.github %} can display several common image formats, including PNG, JPG, GIF, PSD, and SVG. In addition to simply displaying them, there are several ways to compare differences between versions of those image formats. > [!NOTE] > * {% data variables.product.prodname_dotcom %} does not support comparing the differences between PSD files. @@ -70,9 +70,9 @@ You can visually compare images in three different modes: [2-up](#2-up), [swipe] ## 3D File Viewer -{% data variables.product.product_name %} can host and render 3D files with the _.stl_ extension. +{% data variables.product.github %} can host and render 3D files with the _.stl_ extension. -When looking directly at an STL file on {% data variables.product.product_name %} you can: +When looking directly at an STL file on {% data variables.product.github %} you can: * Click and drag to spin the model. * Right click and drag to translate the view. @@ -149,7 +149,7 @@ Currently, links within PDFs are ignored. Commits and pull requests that include prose documents have the ability to represent those documents with _source_ and _rendered_ views. The source view shows the raw text that has been typed, while the rendered -view shows how that text would look once it's rendered on {% data variables.product.product_name %}. For example, +view shows how that text would look once it's rendered on {% data variables.product.github %}. For example, this might be the difference between showing `**bold**` in Markdown, and **bold** in the rendered view. Prose rendering is supported for rendered documents supported by [github/markup](https://github.com/github/markup): @@ -195,23 +195,23 @@ of your rendered prose diff to specific sections. ### Viewing complex diffs -Some pull requests involve a large number of changes with large, complex documents. When the changes take too long to analyze, {% data variables.product.product_name %} can't always produce a rendered view of the changes. If this happens, you'll see an error message when you click the rendered button. +Some pull requests involve a large number of changes with large, complex documents. When the changes take too long to analyze, {% data variables.product.github %} can't always produce a rendered view of the changes. If this happens, you'll see an error message when you click the rendered button. You can still use the source view to analyze and comment on changes. ### Viewing HTML elements -We don't directly support rendered views of commits to HTML documents. Some formats, such as Markdown, let you embed arbitrary HTML in a document. When these documents are shown on {% data variables.product.product_name %}, some of that embedded HTML can be shown in a preview, while some (like an embedded YouTube video) cannot. +We don't directly support rendered views of commits to HTML documents. Some formats, such as Markdown, let you embed arbitrary HTML in a document. When these documents are shown on {% data variables.product.github %}, some of that embedded HTML can be shown in a preview, while some (like an embedded YouTube video) cannot. -In general, rendered views of changes to a document containing embedded HTML will show changes to the elements that are supported in {% data variables.product.product_name %}'s view of the document. Changes to documents containing embedded HTML should always be reviewed in both the rendered and source views for completeness. +In general, rendered views of changes to a document containing embedded HTML will show changes to the elements that are supported in {% data variables.product.github %}'s view of the document. Changes to documents containing embedded HTML should always be reviewed in both the rendered and source views for completeness. ## Mapping GeoJSON/TopoJSON files on {% data variables.product.prodname_dotcom %} -{% data variables.product.product_name %} supports rendering GeoJSON and TopoJSON map files within {% data variables.product.product_name %} repositories. Commit the file as you would normally using a `.geojson` or `.topojson` extension. Files with a `.json` extension are also supported, but only if `type` is set to `FeatureCollection`, `GeometryCollection`, or `topology`. Then, navigate to the path of the GeoJSON/TopoJSON file on {% data variables.product.product_name %}. +{% data variables.product.github %} supports rendering GeoJSON and TopoJSON map files within {% data variables.product.github %} repositories. Commit the file as you would normally using a `.geojson` or `.topojson` extension. Files with a `.json` extension are also supported, but only if `type` is set to `FeatureCollection`, `GeometryCollection`, or `topology`. Then, navigate to the path of the GeoJSON/TopoJSON file on {% data variables.product.github %}. ### Geometry types -Maps on {% data variables.product.product_name %} use [Leaflet.js](http://leafletjs.com) and support all the geometry types outlined in [the geoJSON spec](http://www.geojson.org/geojson-spec.html) (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection). TopoJSON files should be type "Topology" and adhere to the [TopoJSON spec](https://github.com/mbostock/topojson/wiki/Specification). +Maps on {% data variables.product.github %} use [Leaflet.js](http://leafletjs.com) and support all the geometry types outlined in [the geoJSON spec](http://www.geojson.org/geojson-spec.html) (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection). TopoJSON files should be type "Topology" and adhere to the [TopoJSON spec](https://github.com/mbostock/topojson/wiki/Specification). {% ifversion geoJSON-with-MapBox %} @@ -233,7 +233,7 @@ See [version 1.1.0 of the open simplestyle spec](https://github.com/mapbox/simpl ### Embedding your map elsewhere -Want to make your GeoJSON map available someplace other than {% data variables.product.product_name %}? Simply modify this template, and place it in any HTML page that supports JavaScript (for example, [{% data variables.product.prodname_pages %}](https://pages.github.com)): +Want to make your GeoJSON map available someplace other than {% data variables.product.github %}? Simply modify this template, and place it in any HTML page that supports JavaScript (for example, [{% data variables.product.prodname_pages %}](https://pages.github.com)): ```html @@ -266,7 +266,7 @@ The underlying map data (street names, roads, etc.) are driven by [OpenStreetMap ### Troubleshooting GeoJSON/TopoJSON files -If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). If your points aren't appearing where you'd expect (for example, in the middle of the ocean), it's likely that the data is in a projection which is currently unsupported. Currently, {% data variables.product.product_name %} only supports the `urn:ogc:def:crs:OGC:1.3:CRS84` projection. +If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). If your points aren't appearing where you'd expect (for example, in the middle of the ocean), it's likely that the data is in a projection which is currently unsupported. Currently, {% data variables.product.github %} only supports the `urn:ogc:def:crs:OGC:1.3:CRS84` projection. Additionally, if your `.geojson` file is especially large (over 10 MB), it is not possible to render within the browser. If that's the case, you'll generally see a message that says we can't show files that large. @@ -307,7 +307,7 @@ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb ## Displaying Mermaid files on {% data variables.product.prodname_dotcom %} -{% data variables.product.product_name %} supports rendering Mermaid files within repositories. Commit the file as you would normally using a `.mermaid` or `.mmd` extension. Then, navigate to the path of the Mermaid file on {% data variables.product.prodname_dotcom %}. +{% data variables.product.github %} supports rendering Mermaid files within repositories. Commit the file as you would normally using a `.mermaid` or `.mmd` extension. Then, navigate to the path of the Mermaid file on {% data variables.product.prodname_dotcom %}. For example, if you add a `.mmd` file with the following content to your repository: From d3fbc0fa54e54f4ce6228083e0bea7b5ec706f01 Mon Sep 17 00:00:00 2001 From: Joshua Walker <3141202+joshuawalker@users.noreply.github.com> Date: Tue, 21 Jan 2025 23:33:02 +1300 Subject: [PATCH 5/5] Add troubleshooting adding an email section (#53947) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> --- ...an-email-address-to-your-github-account.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 6471852eef92..9a2f8685b1d4 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -26,7 +26,32 @@ shortTitle: Add an email address {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} -{% data reusables.user-settings.select_primary_email %} +1. If you'd like to associate the email address with your web-based Git operations, select it from the "Primary email address" dropdown menu. + + ![Screenshot of the "Email" settings page. Under "Primary email address," a dropdown menu, labeled with Octocat's email address, is outlined in orange.](/assets/images/help/settings/email-primary.png) + +## Troubleshooting adding an email + +If you see an error message when you try to add an email address to your account, you may be experiencing one of the following issues. + +### Email already in use + +If you see the error message `Error adding EMAIL: email is already in use`, it means the email address is already linked to another {% data variables.product.prodname_dotcom %} account. An email address can only be associated with one {% data variables.product.prodname_dotcom %} account at a time. + +To use this email with a different account, follow these steps: + +1. Sign in to the account currently linked to the email address and remove it from that account. +1. If you don’t have access to the account, request a password reset email to recover it. See [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials). + +### Email linked to a {% data variables.enterprise.prodname_managed_user %} + +If the email address that you are trying to add is provided to you by your organization, you may see the `Error adding EMAIL: email is already in use` error when your organization has created a {% data variables.enterprise.prodname_managed_user %} for you in their {% data variables.enterprise.prodname_emu_enterprise %}. + +Reach out to your site administrator or internal IT helpdesk to learn about their deployment of {% data variables.product.prodname_ghe_cloud %} and how to access the account. You may be able to sign into the {% data variables.product.prodname_ghe_cloud %} application via the organization's identity provider (IdP). + +If you want to use your email address with a personal account, you must sign in to your {% data variables.enterprise.prodname_managed_user %} and unverify the email in your account settings. The email will remain linked to your {% data variables.enterprise.prodname_managed_user %}, allowing you to access the account through your organization's IdP. + +However, some third-party apps or services may not function properly with a {% data variables.enterprise.prodname_managed_user %} that has an unverified email address. ## Further reading