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

Remove mentions of Projects (classic) and associated features (#55017)

Browse Source
This commit is contained in:
Cam McHenry
2025-04-10 08:57:40 -04:00
committed by GitHub
parent 9a1acb990e
commit 1d7c2feb80
24 changed files with 64 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/actions/security-for-github-actions/security-guides/automatic-token-authentication.md
View File

@@ -95,7 +95,9 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
| packages | read/write | read | read |
| pages | read/write | none | read |
| pull-requests | read/write | none | read |
| {% ifversion projects-v1 %} |
| repository-projects | read/write | none | read |
| {% endif %} |
| security-events | read/write | none | read |
| statuses | read/write | none | read |

2
content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
View File

@@ -49,7 +49,7 @@ The events listed in your security log are triggered by your actions. Actions ar
| {% endif %} |
| `personal_access_token` | Contains activities related to {% data variables.product.pat_v2 %}s. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). |
| `profile_picture`| Contains all activities related to your profile picture. |
| `project` | Contains all activities related to {% data variables.projects.projects_v1_boards %}. |
| `project` | Contains all activities related to {% data variables.projects.projects_v2 %}. |
| `public_key` | Contains all activities related to [your public SSH keys](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account). |
| `repo`| Contains all activities related to the repositories you own. |
| {% ifversion fpt or ghec %} |

1
content/code-security/dependabot/troubleshooting-dependabot/troubleshooting-dependabot-on-github-actions.md
View File

@@ -92,7 +92,6 @@ on: pull_request
permissions:
pull-requests: write
issues: write
repository-projects: write
...
jobs:

2
content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
View File

@@ -56,7 +56,6 @@ on: pull_request
permissions:
pull-requests: write
issues: write
repository-projects: write
jobs:
dependabot:
@@ -93,7 +92,6 @@ on: pull_request
permissions:
pull-requests: write
issues: write
repository-projects: write
jobs:
dependabot:

8
content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
View File

@@ -30,8 +30,8 @@ When you block a user:
* You are removed as a collaborator on their repositories
* Their sponsorship of you is canceled
* Any pending repository or account successor invitations to or from the blocked user are canceled
* The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you
* You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user
* The user is removed as a collaborator from all the projects owned by you
* You are removed as a collaborator from all the projects owned by the user
After you've blocked a user, they cannot:
* Send you any notifications, including by [@mentioning](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#mentioning-people-and-teams) your username
@@ -44,8 +44,8 @@ After you've blocked a user, they cannot:
* Cross-reference your repositories in comments
* Fork, watch, pin, or star your repositories
* Sponsor you
* Add you as a collaborator on their projects and {% data variables.projects.projects_v1_boards %}
* Make changes to your public projects and {% data variables.projects.projects_v1_boards %}
* Add you as a collaborator on their projects
* Make changes to your public projects
In repositories you own, blocked users also cannot:
* Open issues

2
content/issues/planning-and-tracking-with-projects/creating-projects/index.md
View File

@@ -1,7 +1,7 @@
---
title: 'Creating {% data variables.projects.projects_v2 %}'
shortTitle: 'Creating {% data variables.projects.projects_v2 %}'
intro: 'Learn about creating projects and migrating your {% data variables.projects.projects_v1_boards %}.'
intro: 'Learn about creating projects and copying existing projects.'
versions:
feature: projects-v2
topics:

4
content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md
View File

@@ -16,7 +16,7 @@ redirect_from:
You can use {% data variables.product.prodname_dotcom %} repositories, issues, projects, and other tools to plan and track your work, whether working on an individual project or cross-functional team.
In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates and forms, open issues and use task lists to break down work, and establish a {% data variables.projects.projects_v1_board %} for organizing and tracking issues.
In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates and forms, open issues and use task lists to break down work, and establish a {% data variables.projects.project_v2 %} for organizing and tracking issues.
## Creating a repository
@@ -153,7 +153,7 @@ Below is an example of a `front-end` label that we created and added to the issu
![Screenshot of an issue called "Front-end work for Project Octocat." In the right sidebar, in the "Labels" section, the "front-end" label is applied.](/assets/images/help/issues/quickstart-add-label-to-issue.png)
## Adding issues to a {% data variables.projects.projects_v2 %}
## Adding issues to a {% data variables.projects.project_v2 %}
You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects).

2
content/migrations/using-ghe-migrator/about-ghe-migrator.md
View File

@@ -43,7 +43,9 @@ The items in the table below can be migrated with a repository. Any items not sh
| Wikis | All wiki data is migrated.
| Teams | **@mentions** of teams are rewritten to match the target.
| Milestones | Timestamps are preserved.
| {% ifversion projects-v1 %} |
| {% data variables.product.prodname_projects_v1_caps %} boards | {% data variables.projects.projects_v1_boards_caps %} associated with the repository and with the organization that owns the repository are migrated. {% data variables.product.prodname_projects_v2 %}, the all-new projects experience, is not supported.
| {% endif %} |
| Issues | Issue references and timestamps are preserved.
| Issue comments | Cross-references to comments are rewritten for the target instance.
| Pull requests | Cross-references to pull requests are rewritten to match the target. Timestamps are preserved.

16
content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md
View File

@@ -75,7 +75,9 @@ The _conflicts.csv_ file contains a _migration map_ of conflicts and recommended
| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` |
| `repository` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename` |
| `team` | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` |
| {% ifversion projects-v1 %} |
| `project` | `https://example-gh.source/octo-org/widgets/projects/1` | `https://example-gh.target/octo-org/projects/1` | `merge` |
| {% endif %} |
Each row in _conflicts.csv_ provides the following information:
@@ -93,10 +95,22 @@ There are several different mapping actions that `ghe-migrator` can take when tr
| `action` | Description | Applicable models |
|------------------------|-------------|-------------------|
| `import` | (default) Data from the source is imported to the target. | All record types
| {% ifversion projects-v1 %} |
| `map` | Instead of creating a new model based on the source data, an existing record in the target is used. Useful for importing a repository into an existing organization or mapping user identities in the target to user identities in the source. | Users, organizations, projects
| {% else %} |
| `map` | Instead of creating a new model based on the source data, an existing record in the target is used. Useful for importing a repository into an existing organization or mapping user identities in the target to user identities in the source. | Users, organizations
| {% endif %} |
| {% ifversion projects-v1 %} |
| `rename` | Data from the source is renamed, then copied over to the target. | Users, organizations, repositories, projects
| {% else %} |
| `rename` | Data from the source is renamed, then copied over to the target. | Users, organizations, repositories
| {% endif %} |
| `map_or_rename` | If the target exists, map to that target. Otherwise, rename the imported model. | Users
| {% ifversion projects-v1 %} |
| `merge` | Data from the source is combined with existing data on the target. | Teams, projects
| {% else %} |
| `merge` | Data from the source is combined with existing data on the target. | Teams
| {% endif %} |
**We strongly suggest you review the _conflicts.csv_ file and use `ghe-migrator audit` to ensure that the proper actions are being taken.** If everything looks good, you can continue.
@@ -195,7 +209,9 @@ The record types match those found in the [migrated data](/migrations/using-ghe-
| Repositories | `repository`
| Teams | `team`
| Milestones | `milestone`
| {% ifversion projects-v1 %} |
| {% data variables.projects.projects_v1_boards_caps %} | `project`
| {% endif %} |
| Issues | `issue`
| Issue comments | `issue_comment`
| Pull requests | `pull_request`

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

@@ -92,7 +92,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
| {% endif %} |
| `personal_access_token` | Contains activities related to {% data variables.product.pat_v2 %}s in your organization. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
| `profile_picture`| Contains all activities related to your organization's profile picture.
| `project` | Contains all activities related to {% data variables.projects.projects_v1_boards %}.
| `project` | Contains all activities related to {% data variables.projects.projects_v2_and_v1 %}.
| `protected_branch` | Contains all activities related to protected branches.
| `repo` | Contains activities related to the repositories owned by your organization.
| {% ifversion fpt or ghec %} |

2
content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
View File

@@ -1,6 +1,6 @@
---
title: 'Disabling projects in your organization'
intro: 'Organization owners can turn off organization-wide {% data variables.projects.projects_v2 %}, organization-wide {% data variables.projects.projects_v1_boards %}, and repository-level {% data variables.projects.projects_v1_boards %} in an organization.'
intro: 'Organization owners can turn off organization-wide {% data variables.projects.projects_v2 %}{% ifversion projects-v1 %}, organization-wide {% data variables.projects.projects_v1_boards %}, and repository-level {% data variables.projects.projects_v1_boards %}{% endif %} in an organization.'
redirect_from:
- /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization
- /articles/disabling-project-boards-in-your-organization

2
content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
View File

@@ -5,7 +5,7 @@ redirect_from:
- /articles/integrating-jira-with-your-organization-project-board
- /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board
versions:
ghes: '*'
feature: projects-v1
shortTitle: Integrate Jira
allowTitleToDifferFromFilename: true
---

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

@@ -110,7 +110,9 @@ Some of the features listed below are limited to organizations using {% data var
| {% endif %} |
| Manage [topics](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics) | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "check" aria-label="Yes" %} |
| Enable wikis and restrict wiki editors | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "check" aria-label="Yes" %} |
| {% ifversion projects-v1 %} |
| Enable {% data variables.projects.projects_v1_boards %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "check" aria-label="Yes" %} |
| {% endif %} |
| Configure [pull request merges](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges) | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "check" aria-label="Yes" %} |
| Configure [a publishing source for {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "x" aria-label="No" %} | {% octicon "check" aria-label="Yes" %} | {% octicon "check" aria-label="Yes" %} |
| {% ifversion copilot %} |

2
content/repositories/creating-and-managing-repositories/transferring-a-repository.md
View File

@@ -23,7 +23,7 @@ topics:
---
## About repository transfers
When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, {% data variables.product.prodname_projects_v1 %}, and settings. You can also change the repository name while transferring a repository. See [AUTOTITLE](/repositories/creating-and-managing-repositories/renaming-a-repository).
When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, {% data variables.projects.projects_v2 %}, and settings. You can also change the repository name while transferring a repository. See [AUTOTITLE](/repositories/creating-and-managing-repositories/renaming-a-repository).
Prerequisites for repository transfers:
* When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}

16
content/rest/using-the-rest-api/issue-event-types.md
View File

@@ -24,6 +24,8 @@ Issue events all have the same object structure, except events that are only ava
{% data reusables.issue-events.issue-event-common-properties %}
{% ifversion projects-v1 %}
## added_to_project
The issue or pull request was added to a {% data variables.projects.projects_v1_board %}. {% data reusables.projects.disabled-projects %}
@@ -47,6 +49,8 @@ This event is available for the following issue types.
{% data reusables.issue-events.issue-event-common-properties %}
{% data reusables.issue-events.project-card-properties %}
{% endif %}
## assigned
The issue or pull request was assigned to a user.
@@ -244,6 +248,8 @@ This event is available for the following issue types.
{% data reusables.issue-events.issue-event-common-properties %}
{% ifversion projects-v1 %}
## converted_note_to_issue
The issue was created by converting a note in a {% data variables.projects.projects_v1_board %} to an issue. {% data reusables.projects.disabled-projects %}
@@ -266,6 +272,8 @@ This event is available for the following issue types.
{% data reusables.issue-events.issue-event-common-properties %}
{% data reusables.issue-events.project-card-properties %}
{% endif %}
## converted_to_discussion
The issue was closed and converted to a discussion.
@@ -556,6 +564,8 @@ This event is available for the following issue types.
`milestone` | `object` | The milestone object.
`milestone[title]` | `string` | The title of the milestone.
{% ifversion projects-v1 %}
## moved_columns_in_project
The issue or pull request was moved between columns in a {% data variables.projects.projects_v1_board %}. {% data reusables.projects.disabled-projects %}
@@ -580,6 +590,8 @@ This event is available for the following issue types.
{% data reusables.issue-events.project-card-properties %}
`previous_column_name` | `string` | The name of the column the issue was moved from.
{% endif %}
## pinned
The issue was pinned.
@@ -635,6 +647,8 @@ This event is available for the following issue types.
{% data reusables.issue-events.issue-event-common-properties %}
{% ifversion projects-v1 %}
## removed_from_project
The issue or pull request was removed from a {% data variables.projects.projects_v1_board %}. {% data reusables.projects.disabled-projects %}
@@ -658,6 +672,8 @@ This event is available for the following issue types.
{% data reusables.issue-events.issue-event-common-properties %}
{% data reusables.issue-events.project-card-properties %}
{% endif %}
## renamed
The issue or pull request title was changed.

4
content/search-github/searching-on-github/searching-issues-and-pull-requests.md
View File

@@ -198,7 +198,9 @@ You can use the `project` qualifier to find issues that are associated with a sp
| Qualifier | Example
| ------------- | -------------
| <code>project:<em>PROJECT_NUMBER</em></code> | **project:github/57** matches issues owned by GitHub that are associated with the organization's project 57.
| {% ifversion projects-v1 %} |
| <code>project:<em>REPOSITORY/PROJECT_NUMBER</em></code> | **project:github-linguist/linguist/1** matches issues that are associated with project 1 in @github's linguist repository.
| {% endif %} |
## Search by commit status
@@ -367,7 +369,7 @@ You can narrow your search to issues and pull requests that are missing certain
| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels.
| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint."
| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories.
| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a {% data variables.projects.projects_v1_board %}, containing the word "build."
| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a {% data variables.projects.project_v2 %}, containing the word "build."
## Further reading

2
data/features/projects-v1-can-create.yml
View File

@@ -2,4 +2,4 @@
# Can the user create a Project (classic)?
# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
versions:
ghes: '*'
ghes: '<=3.16'

2
data/features/projects-v1-create-repo-project.yml
View File

@@ -1,3 +1,3 @@
# Ability to create new repository level projects (classic)
versions:
ghes: '*'
ghes: '<=3.16'

2
data/features/projects-v1.yml
View File

@@ -2,4 +2,4 @@
# Projects (classic)
# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
versions:
ghes: '*'
ghes: '<=3.16'

4
data/features/projects-v2-migration.yml
View File

@@ -1,5 +1,3 @@
# Migrating from projects (classic)
versions:
fpt: '*'
ghec: '*'
ghes: '>=3.13'
ghes: '>=3.13 <=3.16'

4
data/reusables/actions/github-token-available-permissions.md
View File

@@ -12,8 +12,8 @@ permissions:
discussions: read|write|none
packages: read|write|none
pages: read|write|none
pull-requests: read|write|none
repository-projects: read|write|none
pull-requests: read|write|none{% ifversion projects-v1 %}
repository-projects: read|write|none{% endif %}
security-events: read|write|none
statuses: read|write|none
```

2
data/reusables/actions/github-token-scope-descriptions.md
View File

@@ -19,6 +19,8 @@ Available permissions and details of what each allows an action to do:
| `packages` | Work with GitHub Packages. For example, `packages: write` permits an action to upload and publish packages on GitHub Packages. For more information, see [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries). |
| `pages` | Work with GitHub Pages. For example, `pages: write` permits an action to request a GitHub Pages build. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-pages). |
| `pull-requests` | Work with pull requests. For example, `pull-requests: write` permits an action to add a label to a pull request. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-pull-requests). |
| {% ifversion projects-v1 %} |
| `repository-projects` | Work with GitHub projects (classic). For example, `repository-projects: write` permits an action to add a column to a project (classic). For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-projects). |
| {% endif %} |
| `security-events` | Work with GitHub code scanning and Dependabot alerts. For example, `security-events: read` permits an action to list the Dependabot alerts for the repository, and `security-events: write` allows an action to update the status of a code scanning alert. For more information, see [Repository permissions for 'Code scanning alerts'](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-code-scanning-alerts) and [Repository permissions for 'Dependabot alerts'](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-dependabot-alerts) in "Permissions required for GitHub Apps." |
| `statuses` | Work with commit statuses. For example, `statuses:read` permits an action to list the commit statuses for a given reference. For more information, see [AUTOTITLE](/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-commit-statuses). |

2
data/reusables/audit_log/audit-log-action-categories.md
View File

@@ -83,7 +83,7 @@
| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an organization. For more information, see [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning). |
| `organization_default_label` | Contains activities related to default labels for repositories in an organization. |
| `organization_domain` | Contains activities related to verified organization domains. |
| `organization_projects_change` | Contains activities related to organization-wide {% data variables.projects.projects_v1_boards %} in an enterprise. |
| `organization_projects_change` | Contains activities related to organization-wide {% data variables.projects.projects_v2_and_v1 %} in an enterprise. |
| {% ifversion fpt or ghec %} |
| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. |
| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. |

4
data/reusables/enterprise-migration-tool/data-not-migrated.md
View File

@@ -10,8 +10,8 @@
* GitHub Apps and GitHub App installations
* {% data variables.large_files.product_name_short %} objects and large binaries (repositories using {% data variables.large_files.product_name_short %} are still supported, see [Limitations of {% data variables.product.prodname_importer_proper_name %}](#limitations-of-github-enterprise-importer))
* Links from commits to pull requests that were rebase merged
* Packages in {% data variables.product.prodname_registry %}
* Projects (classic) at the organization level
* Packages in {% data variables.product.prodname_registry %}{% ifversion projects-v1 %}
* Projects (classic) at the organization level{% endif %}
* {% data variables.product.prodname_projects_v2 %} (the new projects experience)
* References between pull requests and issues in different repositories (see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls))
* Remediation states of {% data variables.product.prodname_secret_scanning %} results