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

Hack Week 2025: update product.product_name in various folders (ii) (#54023)

Browse Source
This commit is contained in:
Anne-Marie
2025-01-24 20:44:49 +00:00
committed by GitHub
parent 6f86160ad7
commit 3e978c1356
21 changed files with 39 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/github-cli/github-cli/using-github-cli-extensions.md
View File

@@ -12,7 +12,7 @@ topics:
## About {% data variables.product.prodname_cli %} extensions
> [!NOTE]
> Extensions outside of {% data variables.product.product_name %} and {% data variables.product.prodname_cli %} are not certified by {% data variables.product.product_name %} and are governed by separate terms of service, privacy policy, and support documentation. To mitigate risk when using third-party extensions, audit the source code of the extension before installing or updating the extension.
> Extensions outside of {% data variables.product.github %} and {% data variables.product.prodname_cli %} are not certified by {% data variables.product.github %} and are governed by separate terms of service, privacy policy, and support documentation. To mitigate risk when using third-party extensions, audit the source code of the extension before installing or updating the extension.
{% data reusables.cli.cli-extensions %} For more information about how to create {% data variables.product.prodname_cli %} extensions, see [AUTOTITLE](/github-cli/github-cli/creating-github-cli-extensions).

2
content/graphql/guides/migrating-graphql-global-node-ids.md
View File

@@ -11,7 +11,7 @@ shortTitle: Migrating global node IDs
## Background
The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be {% data variables.release-phases.closing_down %} and replaced with a new format. This guide shows you how to migrate to the new format, if necessary.
The {% data variables.product.github %} GraphQL API currently supports two types of global node ID formats. The legacy format will be {% data variables.release-phases.closing_down %} and replaced with a new format. This guide shows you how to migrate to the new format, if necessary.
By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are {% data variables.release-phases.closing_down %}.

2
content/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api.md
View File

@@ -133,7 +133,7 @@ These two examples show how to calculate the total nodes in a call.
{% ifversion ghes %}
Rate limits are disabled by default for {% data variables.product.product_name %}. Contact your site administrator to confirm the rate limits for your instance.
Rate limits are disabled by default for {% data variables.product.prodname_ghe_server %}. Contact your site administrator to confirm the rate limits for your instance.
If you are a site administrator, you can set rate limits for your instance. For more information, see [AUTOTITLE](/admin/configuration/configuring-user-applications-for-your-enterprise/configuring-rate-limits).

2
content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
View File

@@ -1,6 +1,6 @@
---
title: 'About {% data variables.product.prodname_projects_v1 %}'
intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. {% ifversion projects-v1-can-create %} You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.{% endif %}'
intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.github %} help you organize and prioritize your work. {% ifversion projects-v1-can-create %} You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.{% endif %}'
redirect_from:
- /github/managing-your-work-on-github/managing-project-boards/about-project-boards
- /articles/about-projects

2
content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
View File

@@ -23,7 +23,7 @@ You can add issue or pull request cards to your {% data variables.projects.proje
You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
> [!NOTE]
> You can also add notes to your {% data variables.projects.projects_v1_board %} to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. For more information, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board).
> You can also add notes to your {% data variables.projects.projects_v1_board %} to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.github %}, or to add related information to your {% data variables.projects.projects_v1_board %}. For more information, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board).
{% data reusables.project-management.edit-in-project %}

2
content/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically.md
View File

@@ -28,7 +28,7 @@ The auto-add workflow supports a subset of filters. You can use the following fi
| `is` | open, closed, merged, draft, issue, pr
| `label` | "label name"
| `reason` | completed, reopened, "not planned"
| `assignee` | {% data variables.product.product_name %} username
| `assignee` | {% data variables.product.github %} username
| `no` | label, assignee, reason
All filters, other than `no`, support negation. For example, you could use `-label:bug` to add issues that do not have the "bug" label.

8
content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
View File

@@ -554,7 +554,7 @@ The response will contain the node ID of the newly created draft issue.
### Updating a project's settings
The following example will update your project's settings. Replace `PROJECT_ID` with the node ID of your project. Set `public` to `true` to make your project public on {% data variables.product.product_name %}. Modify `readme` to make changes to your project's README.
The following example will update your project's settings. Replace `PROJECT_ID` with the node ID of your project. Set `public` to `true` to make your project public on {% data variables.product.github %}. Modify `readme` to make changes to your project's README.
{% curl %}
@@ -770,9 +770,9 @@ gh api graphql -f query='
You can use a mutation to create a new project. For more information, see [AUTOTITLE](/graphql/guides/forming-calls-with-graphql#about-mutations).
To create a new project using the API, you'll need to provide a name for the project and the node ID of a {% data variables.product.product_name %} user or organization who will become the project's owner.
To create a new project using the API, you'll need to provide a name for the project and the node ID of a {% data variables.product.github %} user or organization who will become the project's owner.
You can find the node ID of a {% data variables.product.product_name %} user or organization if you know the username. Replace <code>GITHUB_OWNER</code> with the {% data variables.product.product_name %} username of the new project owner.
You can find the node ID of a {% data variables.product.github %} user or organization if you know the username. Replace <code>GITHUB_OWNER</code> with the {% data variables.product.github %} username of the new project owner.
{% curl %}
@@ -828,4 +828,4 @@ gh api graphql -f query='
## Using webhooks
You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.product_name %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see [AUTOTITLE](/webhooks-and-events/webhooks/about-webhooks). To learn more about the `projects_v2_item` webhook event, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item).
You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.github %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see [AUTOTITLE](/webhooks-and-events/webhooks/about-webhooks). To learn more about the `projects_v2_item` webhook event, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item).

2
content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project.md
View File

@@ -63,7 +63,7 @@ You can quickly clear the same field for multiple items.
## Undoing bulk changes in a table
When you make a bulk change in the table layout, {% data variables.product.product_name %} will display the option to undo that change.
When you make a bulk change in the table layout, {% data variables.product.github %} will display the option to undo that change.
1. Make a bulk change to your table.
1. When the notice appears in the lower right of your table, click **Undo**.

2
content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
View File

@@ -30,7 +30,7 @@ Teams are granted read permissions on any project they are added to. This permis
1. In the search field, start typing the name of the project you want to add and then select the project in the list of matches.
> [!NOTE]
> If this change will result in increased project permissions for the team's members, {% data variables.product.product_name %} will prompt you to confirm your choice.
> If this change will result in increased project permissions for the team's members, {% data variables.product.github %} will prompt you to confirm your choice.
## Removing a project from a team

2
content/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md
View File

@@ -1,6 +1,6 @@
---
title: Filtering and searching issues and pull requests
intro: 'To find detailed information about a repository on {% data variables.product.product_name %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.'
intro: 'To find detailed information about a repository on {% data variables.product.github %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.'
redirect_from:
- /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees
- /articles/filtering-issues-and-pull-requests-by-assignees

2
content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
View File

@@ -23,7 +23,7 @@ Your issue and pull request dashboards are available at the top of any page. On
{% ifversion global-nav-update %}
1. At the top of any page, click {% octicon "issue-opened" aria-label="Issues" %} to see your issues or {% octicon "git-pull-request" aria-label="Pull requests" %} to see your pull requests.
![Screenshot of the header of any page on {% data variables.product.product_name %}. The "Pull requests" and "Issues" icons are outlined in dark orange.](/assets/images/help/navigation/issues-and-prs-new-navigation.png)
![Screenshot of the header of any page on {% data variables.product.github %}. The "Pull requests" and "Issues" icons are outlined in dark orange.](/assets/images/help/navigation/issues-and-prs-new-navigation.png)
{% else %}
1. At the top of any page, click **Pull requests** or **Issues**.

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

@@ -32,11 +32,11 @@ type: how_to
---
## About labels
You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository.
You can manage your work on {% data variables.product.github %} by creating labels to categorize {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository.
## About default labels
{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository.
{% data variables.product.github %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository.
Label | Description
--- | ---

2
content/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer.md
View File

@@ -17,7 +17,7 @@ shortTitle: Import a repository
{% data variables.product.prodname_importer %} imports the source code and commit history of Git repositories hosted on external hosting services. For more information about the capabilities and limitations of {% data variables.product.prodname_importer %}, see [AUTOTITLE](/migrations/importing-source-code/using-github-importer/about-github-importer#capabilities-and-limitations-of-github-importer).
{% data variables.product.product_name %} uses the email address in the commit header to link a commit to a {% data variables.product.prodname_dotcom %} user. To correctly attribute commits in an imported repository, users will need to add the email address associated with their commits to their account on {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).
{% data variables.product.github %} uses the email address in the commit header to link a commit to a {% data variables.product.github %} user. To correctly attribute commits in an imported repository, users will need to add the email address associated with their commits to their {% data variables.product.github %} account. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).
## Importing a repository with {% data variables.product.prodname_importer %}

4
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/about-source-code-imports-using-the-command-line.md
View File

@@ -1,6 +1,6 @@
---
title: About source code imports using the command line
intro: 'You can use command line tools to import source code and its revision history to {% data variables.product.product_name %}.'
intro: 'You can use command line tools to import source code and its revision history to {% data variables.product.github %}.'
versions:
fpt: '*'
ghes: '*'
@@ -24,7 +24,7 @@ You can use the command line to import source code and, if the code has been tra
* To import a Git repository that is stored on a code hosting service{% ifversion fpt or ghec %} that is not accessible from the public internet{% endif %}, see [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line).
* To import code that is only stored locally, and is either tracked by Git or not tracked by any version control system, see [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/adding-locally-hosted-code-to-github).
* To import code that is tracked by any version control system other than Git, first convert the repository to Git, then push the Git repository to {% data variables.product.product_name %}.
* To import code that is tracked by any version control system other than Git, first convert the repository to Git, then push the Git repository to {% data variables.product.github %}.
{% ifversion fpt or ghec %}
* [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository)
* [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository)

14
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/adding-locally-hosted-code-to-github.md
View File

@@ -1,6 +1,6 @@
---
title: Adding locally hosted code to GitHub
intro: 'If your code is stored locally on your computer and is tracked by Git or not tracked by any version control system (VCS), you can import the code to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %} or Git commands.'
intro: 'If your code is stored locally on your computer and is tracked by Git or not tracked by any version control system (VCS), you can import the code to {% data variables.product.github %} using {% data variables.product.prodname_cli %} or Git commands.'
redirect_from:
- /articles/add-an-existing-project-to-github
- /articles/adding-an-existing-project-to-github-using-the-command-line
@@ -15,19 +15,19 @@ versions:
shortTitle: Local code
---
## About importing source code to {% data variables.product.product_name %}
## About importing source code
{% data reusables.repositories.importing-context %}
{% data reusables.repositories.sensitive-info-warning %}
### Adding existing source code to {% data variables.product.product_name %}
### Adding existing source code to {% data variables.product.github %}
If you have source code stored locally on your computer that is tracked by Git or not tracked by any version control system (VCS), you can add the code to {% data variables.product.product_name %} by typing commands in a terminal. You can do this by typing Git commands directly. Alternatively, you can use {% data variables.product.prodname_cli %} or {% data variables.product.prodname_desktop %}.
If you have source code stored locally on your computer that is tracked by Git or not tracked by any version control system (VCS), you can add the code to {% data variables.product.github %} by typing commands in a terminal. You can do this by typing Git commands directly. Alternatively, you can use {% data variables.product.prodname_cli %} or {% data variables.product.prodname_desktop %}.
#### Using {% data variables.product.prodname_cli %}
{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see [AUTOTITLE](/github-cli/github-cli/about-github-cli).
{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.github %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see [AUTOTITLE](/github-cli/github-cli/about-github-cli).
#### Using {% data variables.product.prodname_desktop %}
@@ -35,7 +35,7 @@ If you're most comfortable with a point-and-click user interface, consider addin
### Converting repositories from other VCS
If your source code is tracked by a different VCS, such as Mercurial, Subversion, or Team Foundation Version Control, you must convert the repository to Git before you can add the project to {% data variables.product.product_name %}.
If your source code is tracked by a different VCS, such as Mercurial, Subversion, or Team Foundation Version Control, you must convert the repository to Git before you can add the project to {% data variables.product.github %}.
* [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository)
* [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository)
@@ -77,7 +77,7 @@ If your locally-hosted code isn't tracked by any VCS, the first step is to initi
## Importing a Git repository with the command line
After you've initialized a Git repository, you can push the repository to {% data variables.product.product_name %}, using either {% data variables.product.prodname_cli %} or Git.
After you've initialized a Git repository, you can push the repository to {% data variables.product.github %}, using either {% data variables.product.prodname_cli %} or Git.
* [Adding a local repository to {% data variables.product.prodname_dotcom %} with {% data variables.product.prodname_cli %}](#adding-a-local-repository-to-github-with-github-cli)
* [Adding a local repository to {% data variables.product.prodname_dotcom %} using Git](#adding-a-local-repository-to-github-using-git)

2
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository.md
View File

@@ -1,6 +1,6 @@
---
title: Importing a Mercurial repository
intro: 'You can import a repository from Mercurial by converting the repository to Git, then pushing the Git repository to {% data variables.product.product_name %}.'
intro: 'You can import a repository from Mercurial by converting the repository to Git, then pushing the Git repository to {% data variables.product.github %}.'
versions:
fpt: '*'
ghes: '*'

2
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository.md
View File

@@ -1,6 +1,6 @@
---
title: Importing a Subversion repository
intro: 'You can import a repository from Subversion by converting the repository to Git, then pushing the Git repository to {% data variables.product.product_name %}.'
intro: 'You can import a repository from Subversion by converting the repository to Git, then pushing the Git repository to {% data variables.product.github %}.'
versions:
fpt: '*'
ghes: '*'

2
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository.md
View File

@@ -1,6 +1,6 @@
---
title: Importing a Team Foundation Version Control repository
intro: 'You can import a repository from Team Foundation Version Control (TFVC) by converting the repository to Git, then pushing the Git repository to {% data variables.product.product_name %}.'
intro: 'You can import a repository from Team Foundation Version Control (TFVC) by converting the repository to Git, then pushing the Git repository to {% data variables.product.github %}.'
versions:
fpt: '*'
ghes: '*'

8
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line.md
View File

@@ -15,7 +15,7 @@ shortTitle: External Git repo
---
Before you start, make sure you know:
* Your {% data variables.product.product_name %} username
* Your {% data variables.product.github %} username
* The clone URL for the external repository, such as `https://external-host.com/user/repo.git` or `git://external-host.com/user/repo.git` (perhaps with a `user@` in front of the `external-host.com` domain name)
> [!NOTE]
@@ -23,10 +23,10 @@ Before you start, make sure you know:
>
> * An external account named **extuser**
> * An external Git host named `https://external-host.com`
> * A {% data variables.product.product_name %} personal account named **ghuser**
> * A {% data variables.product.github %} personal account named **ghuser**
> * A repository on {% data variables.location.product_location %} named **repo.git**
1. [Create a new repository on {% data variables.product.product_name %}](/repositories/creating-and-managing-repositories/creating-a-new-repository). You'll import your external Git repository to this new repository.
1. [Create a new repository on {% data variables.product.github %}](/repositories/creating-and-managing-repositories/creating-a-new-repository). You'll import your external Git repository to this new repository.
1. On the command line, make a "bare" clone of the external repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data.
```shell
@@ -34,7 +34,7 @@ Before you start, make sure you know:
# Makes a bare clone of the external repository in a local directory
```
1. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
1. Push the locally cloned repository to {% data variables.product.github %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
```shell
$ cd REPO.git

10
content/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud.md
View File

@@ -67,17 +67,17 @@ To migrate a repository, you must be an organization owner for the destination o
{% data reusables.enterprise-migration-tool.grant-migrator-tasks %} For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/managing-access-for-a-migration-from-azure-devops#about-the-migrator-role).
{% data reusables.enterprise-migration-tool.confirm-migrator-has-correct-pats %} For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/managing-access-for-a-migration-from-azure-devops#required-scopes-for-personal-access-tokens).
### What organizational structure do we want in {% data variables.product.prodname_dotcom %}?
### What organizational structure do we want in {% data variables.product.github %}?
Next, plan the organizational structure you'll create in {% data variables.product.prodname_dotcom %}. ADO and {% data variables.product.prodname_dotcom %} have different ways of organizing an enterprise's work.
Next, plan the organizational structure you'll create in {% data variables.product.github %}. ADO and {% data variables.product.github %} have different ways of organizing an enterprise's work.
* ADO: Organization > team project > repositories
* {% data variables.product.prodname_dotcom %}: Enterprise > organization > repositories
* {% data variables.product.github %}: Enterprise > organization > repositories
> [!NOTE]
> The concept of a team project, which is used to group repositories in ADO, does not exist in {% data variables.product.prodname_dotcom %}. We do not recommend treating organizations in {% data variables.product.product_name %} as the equivalent of team projects in ADO.
> The concept of a team project, which is used to group repositories in ADO, does not exist in {% data variables.product.github %}. We do not recommend treating organizations in {% data variables.product.github %} as the equivalent of team projects in ADO.
After migrating to {% data variables.product.prodname_dotcom %}, you should have only one enterprise account and a small number of organizations owned by that enterprise. Each organization from ADO should correspond to a single organization on {% data variables.product.prodname_dotcom %}. We do not recommend creating an organization on {% data variables.product.prodname_dotcom %} for each team project on ADO.
After migrating to {% data variables.product.github %}, you should have only one enterprise account and a small number of organizations owned by that enterprise. Each organization from ADO should correspond to a single organization on {% data variables.product.github %}. We do not recommend creating an organization on {% data variables.product.github %} for each team project on ADO.
This may result in a large list of ungrouped repositories within each organization. However, you can manage access to groups of repositories by creating teams. For more information, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams).

2
content/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer.md
View File

@@ -31,7 +31,7 @@ You can migrate on a repository-by-repository basis or, if your migration source
* **High fidelity migration**, which allows you to migrate a single repository, a series of repositories, or an entire organization.
* **Support for custom trial run migrations**, which allow you to run a migration as many times as you desire before running the production migration.
* **Clear and unblocking error logging**, so that migrations are allowed to continue with non-critical migration errors, such as not being able to move a single pull request comment. After the migration, you can review a log file that opens automatically.
* **Users retain ownership of their history**, to ensure that their Git history or {% data variables.product.product_name %} metadata is maintained across the migration.
* **Users retain ownership of their history**, to ensure that their Git history or {% data variables.product.github %} metadata is maintained across the migration.
{% data reusables.enterprise-migration-tool.tool-options %}