projects (classic)에서 마이그레이션

이 문서의 내용

You can migrate your classic project to the new Projects experience.

Notes:

  • If the project you are migrating contains more than 1,200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated.
  • Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "Changing the layout of a view."
  • Automation will not be migrated.
  • Triage, archive, and activity will not be migrated.
  • After migration, the new migrated project and old project will not be kept in sync.

About project migration

You can migrate your project boards to the new Projects experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "About Projects."

Migrating an organization project board

  1. Enable "Project migration" in feature preview. For more information, see "Exploring early access releases with feature preview."

  2. In the top right corner of GitHub.com, click your profile photo, then click Your organizations.

    Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

  3. Click the name of your organization.

  4. Under your organization name, click Projects.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with a table icon and "Projects," is outlined in dark orange.

  5. In the left sidebar, click Projects (classic).

  6. Next to the project you want to migrate, click .

  7. In the menu, click Migrate.

  8. In the popup, select the dropdown menu, then click what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use.

  9. Click Start migration.

Migrating a user project board

  1. Enable "Project migration" in feature preview. For more information, see "Exploring early access releases with feature preview."

  2. In the top right corner of GitHub.com, click your profile photo, then click Your projects.

    Screenshot showing the profile photo menu. The "Your projects" link is highlighted with an orange outline.

  3. On the top of your profile page, in the main navigation, click Projects. Screenshot showing the tabs on a user profile. The 'Projects' tab is highlighted with an orange outline.

  4. Above the list of projects, click Projects (classic).

  5. Next to the project you want to migrate, click .

  6. In the menu, click Migrate.

  7. In the popup, select the dropdown menu, then click what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use.

  8. Click Start migration.

Migrating a repository project board

Note: Projects does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.

  1. Enable "Project migration" in feature preview. For more information, see "Exploring early access releases with feature preview."
  2. On GitHub.com, navigate to the main page of the repository.
  3. Under your repository name, click Projects.
  4. In the left sidebar, click Projects (classic).
  5. Next to the project you want to migrate, click .
  6. In the menu, click Migrate.
  7. In the popup, select the dropdown menu, then click what you want to happen to the project after it is migrated. We recommend selecting "Close the old project" so it's clear which project is in use.
  8. Click Start migration.