Merge pull request github#37450 from github/repo-sync

Repo sync

Author: docs-bot

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

@@ -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 |
 

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

@@ -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 %} |

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

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

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

@@ -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:

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

@@ -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

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

@@ -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:

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

@@ -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).
 

content/migrations/using-ghe-migrator/about-ghe-migrator.md

@@ -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.

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

@@ -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`

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

@@ -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 %} |

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

@@ -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

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

@@ -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
 ---

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

@@ -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 %} |

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

@@ -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 %}

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

@@ -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.

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

@@ -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
 

data/features/projects-v1-can-create.yml

@@ -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'

data/features/projects-v1-create-repo-project.yml

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

data/features/projects-v1.yml

@@ -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'

data/features/projects-v2-migration.yml

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

data/reusables/actions/github-token-available-permissions.md

@@ -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
 ```