Restructure issues content to prepare for Issues 2.0 (#52388)
This commit is contained in:
Felix Guntrip
@@ -16,14 +16,6 @@ topics:
|
||||
- Issues
|
||||
---
|
||||
|
||||
{% ifversion projects-v2-tasklists %}
|
||||
{% note %}
|
||||
|
||||
**Note:** For more information about the new iteration of tasklists, which is currently in beta, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/creating-a-tasklist)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
## About task lists
|
||||
|
||||
A task list is a set of tasks that each render on a separate line with a clickable checkbox. You can select or deselect the checkboxes to mark the tasks as complete or incomplete.
|
||||
|
||||
@@ -20,7 +20,7 @@ featuredLinks:
|
||||
- /codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli
|
||||
popular:
|
||||
- /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
|
||||
- /issues/tracking-your-work-with-issues/creating-an-issue
|
||||
- /issues/tracking-your-work-with-issues/using-issues/creating-an-issue
|
||||
- /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
|
||||
- /repositories/creating-and-managing-repositories/quickstart-for-repositories
|
||||
- /pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
|
||||
|
||||
@@ -11,15 +11,14 @@ versions:
|
||||
includeGuides:
|
||||
- /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
|
||||
- /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
|
||||
- /issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists
|
||||
- /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
|
||||
- /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
|
||||
- /issues/tracking-your-work-with-issues/quickstart
|
||||
- /issues/tracking-your-work-with-issues/creating-an-issue
|
||||
- /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
|
||||
- /issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/configuring-issues/quickstart
|
||||
- /issues/tracking-your-work-with-issues/using-issues/creating-an-issue
|
||||
- /issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project
|
||||
- /issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests
|
||||
- /issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards
|
||||
- /issues/using-labels-and-milestones-to-track-work/managing-labels
|
||||
- /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
|
||||
|
||||
@@ -4,28 +4,26 @@ shortTitle: "{% data variables.product.prodname_github_issues %}"
|
||||
intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
|
||||
introLinks:
|
||||
overview: /issues/tracking-your-work-with-issues/about-issues
|
||||
quickstart: /issues/tracking-your-work-with-issues/quickstart
|
||||
quickstart: /issues/tracking-your-work-with-issues/configuring-issues/quickstart
|
||||
featuredLinks:
|
||||
startHere:
|
||||
- /issues/tracking-your-work-with-issues/creating-an-issue
|
||||
- /issues/tracking-your-work-with-issues/using-issues/creating-an-issue
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
|
||||
- /issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
|
||||
- /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
|
||||
- /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
|
||||
- /issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project
|
||||
guideCards:
|
||||
- /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view
|
||||
- /issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
|
||||
- /issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue
|
||||
- '{% ifversion ghes %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}'
|
||||
- /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
|
||||
popular:
|
||||
- /issues/tracking-your-work-with-issues/about-issues
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects
|
||||
- /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
|
||||
- /issues/managing-your-tasks-with-tasklists/creating-a-tasklist
|
||||
- /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
|
||||
- /issues/using-labels-and-milestones-to-track-work/managing-labels
|
||||
- /issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests
|
||||
- '{% ifversion ghes %}/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards{% endif %}'
|
||||
layout: product-landing
|
||||
beta_product: false
|
||||
@@ -36,7 +34,6 @@ versions:
|
||||
children:
|
||||
- /tracking-your-work-with-issues
|
||||
- /planning-and-tracking-with-projects
|
||||
- /managing-your-tasks-with-tasklists
|
||||
- /organizing-your-work-with-project-boards
|
||||
- /using-labels-and-milestones-to-track-work
|
||||
- /guides
|
||||
|
||||
@@ -1,37 +0,0 @@
|
||||
---
|
||||
title: 'About tasklists'
|
||||
intro: 'You can use tasklists to quickly sketch out projects, divide tasks into subtasks, and track issues and pull requests.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: overview
|
||||
topics:
|
||||
- Issues
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
|
||||
* Tasklists are in private beta and subject to change. We have currently paused onboarding to the beta. Tasklists build upon the previous iteration of [task lists](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists).
|
||||
* For the best experience, we recommend adding no more than 50 tasks to a tasklist and no more than 5 tasklists per issue. There is a hard limit of 250 tasks per tasklist and 10 tasklists per issue.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About tasklists and issue hierarchy
|
||||
|
||||
You can add a tasklist to an issue to quickly break down larger pieces of work into subtasks. You can sketch out a draft of your plans, in either Markdown or in the UI, and optionally convert those draft tasks into real issues or add existing issues and pull requests to your tasklists.
|
||||
|
||||
|
||||
|
||||
When you add issues and pull requests to a tasklist, the tasklist will show metadata associated with the issue or pull request, including any labels applied, the avatars of people assigned, and the open/close state. When you view the issues and pull requests that have been added to a tasklist, {% data variables.product.product_name %} shows which issues are tracking that subtask.
|
||||
|
||||
|
||||
|
||||
Tasklists add support for hierarchies of issues on {% data variables.product.product_name %} by creating relationships between your issues. You can create parent and child relationships, you can also create multiple levels of hierarchy that accurately represent your project by breaking down tasks into exactly the amount of detail that you and your team require.
|
||||
|
||||
|
||||
|
||||
You can create a tasklist using Markdown or using the {% data variables.product.product_name %} UI. Regardless of how you created your tasklist, you can edit it using either Markdown or the UI. For more information, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/creating-a-tasklist)" and "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist)."
|
||||
|
||||
Tasklists also integrate with your projects. {% ifversion projects-v2-tasklists-without-breadcrumbs %}You can{% else %}When you click on an issue in your project, the side-panel opens and displays the issue's place in the hierarchy on a breadcrumb menu, allowing you to navigate through the issues included in your tasklists. You can also{% endif %} add the "Tracks" and "Tracked-by fields" to your project views to quickly see the relationships between your issues. For information, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists)."
|
||||
@@ -1,84 +0,0 @@
|
||||
---
|
||||
title: 'Creating a tasklist'
|
||||
intro: 'You can create a tasklist using the {% data variables.product.product_name %} UI or Markdown.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: tutorial
|
||||
redirect_from:
|
||||
- /early-access/issues/about-tasklists
|
||||
- /issues/tracking-your-work-with-issues/about-tasklists
|
||||
topics:
|
||||
- Issues
|
||||
---
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
## Creating tasklists in the UI
|
||||
|
||||
You can use the **Add tasklist** button to quickly add a tasklist to your issue. The **Add tasklist** button is available when you view or edit an issue.
|
||||
|
||||
1. Navigate to the issue you want to contain your new tasklist. You can also create a new issue.
|
||||
1. At the bottom of the issue description, click {% octicon "plus" aria-hidden="true" %} **Add tasklist**.
|
||||
|
||||
|
||||
|
||||
1. You can then add issues, pull requests, and draft tasks to your new tasklist. For more information, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist)."
|
||||
|
||||
## Creating tasklists with Markdown
|
||||
|
||||
You can create tasklists using Markdown in the issue description (the opening comment of an issue). You can include links to issues and pull requests or create draft issues.
|
||||
|
||||
You can add a tasklist by copying the Markdown below into your issue description:
|
||||
|
||||
````markdown copy
|
||||
```[tasklist]
|
||||
### My tasks
|
||||
- [ ] https://github.com/octo-org/octo-repo/issues/45
|
||||
- [ ] Draft task
|
||||
```
|
||||
````
|
||||
|
||||
You can also use the **Add tasklist** button while editing your issue to insert the Markdown for a tasklist:
|
||||
|
||||
|
||||
|
||||
Once you have started editing your tasklist Markdown, you can add new tasks by preceding each new task with `- [ ] ` and then adding either:
|
||||
|
||||
* A draft task. Draft tasks are text that can later be converted into issues.
|
||||
* The full link to an issue or pull request. For example, `https://github.com/octo-org/octo-repo/issues/45`. If an issue or pull request is in the same repository as your tasklist, you can use the #ISSUE-NUMBER shorthand syntax. For example, `#45`.
|
||||
|
||||
If you add a draft task, it must meet these requirements:
|
||||
|
||||
* Draft tasks can be formatted using Markdown.
|
||||
* Draft tasks must not exceed 512 characters in length.
|
||||
|
||||
Your tasklist will be rendered by {% data variables.product.product_name %} when you preview your changes and when you save the issue. You can then make changes and add issues and draft tasks using the {% data variables.product.product_name %} UI. If you edit the issue description, you will be able to modify the Markdown directly or copy the Markdown to duplicate the tasklist in other issues.
|
||||
|
||||
## Changing the title of a tasklist
|
||||
|
||||
When you create a new tasklist, the default title is "Tasks." You can modify the title by clicking {% octicon "pencil" aria-hidden="true" %} **Rename** in the tasklist's context menu or by editing the issue's markdown.
|
||||
|
||||
1. In the top-right of the issue body, select {% octicon "kebab-horizontal" aria-label="Show options" %} and click **Edit**.
|
||||
|
||||
|
||||
1. In the fenced code block that starts with `` ```[tasklist] ``, add a header with your new title, such as `### My new title`.
|
||||
|
||||
|
||||
|
||||
1. Click **Update comment**.
|
||||
|
||||
## Copying a tasklist
|
||||
|
||||
When you copy your tasklist using the "Copy Markdown" option, {% data variables.product.product_name %} copies Markdown to your clipboard and includes the issue title so you can paste the tasklist outside of GitHub without losing context. See below for an example of a copied Markdown tasklist:
|
||||
|
||||
```markdown
|
||||
- [x] [Design new landing page](https://github.com/octocat/octoproject/issues/4)
|
||||
- [ ] [Translate content into supported languages](https://github.com/octocat/octoproject/issues/11)
|
||||
```
|
||||
|
||||
1. In the top-right of your tasklist, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. In the menu, click **Copy markdown**.
|
||||
@@ -1,18 +0,0 @@
|
||||
---
|
||||
title: 'Managing your issues with tasklists'
|
||||
shortTitle: 'Tasklists'
|
||||
intro: 'You can use tasklists to divide your issues into smaller subtasks.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
topics:
|
||||
- Issues
|
||||
children:
|
||||
- /about-tasklists
|
||||
- /quickstart-for-tasklists
|
||||
- /creating-a-tasklist
|
||||
- /managing-tasks-in-a-tasklist
|
||||
- /using-projects-and-tasklists
|
||||
---
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
@@ -1,69 +0,0 @@
|
||||
---
|
||||
title: 'Managing tasks in a tasklist'
|
||||
intro: 'You can track issues and pull requests as subtasks in a tasklist. You can also add draft tasks and later convert them into issues.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: tutorial
|
||||
topics:
|
||||
- Issues
|
||||
---
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
## Adding tasks to a tasklist
|
||||
|
||||
You can add draft tasks, issues, and pull requests to a tasklist. Draft tasks are useful for quickly capturing ideas that you can later convert into issues. Unlike issues and pull requests that are referenced from your repositories, draft tasks exist only in your tasklist.
|
||||
|
||||
You can add issues and pull requests from any repository you have access to. People who do not have access to the issues and pull requests you add to your tasklist will just see the issue or pull request URL.
|
||||
|
||||
1. At the bottom of your tasklist, click **Add item to Tasks**.
|
||||
|
||||
|
||||
|
||||
1. Add your draft task, issue, or pull request.
|
||||
|
||||
* To add a draft task, just type your task and press <kbd>Enter</kbd>.
|
||||
* To add a recently updated issue, click an issue from the list, or use your arrow keys to select it and then press <kbd>Enter</kbd>.
|
||||
* To search for an issue in the current repository, start typing the title of an issue or the issue's number and click on the result, or use your arrow keys to select it and press <kbd>Enter</kbd>.
|
||||
* To add an issue directly using its URL, paste the URL of an issue and press <kbd>Enter</kbd>.
|
||||
|
||||
## Converting draft tasks to issues in a tasklist
|
||||
|
||||
You can convert draft tasks into issues. Issues are created in the same repository as the issue containing the tasklist.
|
||||
|
||||
1. Place your cursor over the draft task you want to convert and next to the draft task, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. In the menu, click **Convert to issue**.
|
||||
|
||||
## Setting labels, assignees, and projects from a tasklist
|
||||
|
||||
1. Place your cursor over the task you want to make changes to and next to the task, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. Using the context menu, make your changes.
|
||||
* To set labels, select **Set labels**, and then select one or more labels from the menu.
|
||||
* To set assignees, select **Set assignees**, and then select one or more people from the menu.
|
||||
* To add the issue or pull request to a project, select **Set project**, and then select a project from the menu.
|
||||
|
||||
## Dragging tasks to change position and move between tasklists
|
||||
|
||||
You can move tasks within a tasklist and move tasks to other tasklists in the same issue.
|
||||
|
||||
1. Hover your cursor to the left of the task you want to move until a {% octicon "grabber" aria-hidden="true" %} drag handle appears.
|
||||
1. Click on the {% octicon "grabber" aria-hidden="true" %} drag handle and drag the task to the new destination.
|
||||
* Drag the task to another position in the same tasklist.
|
||||
* Drag the task to another tasklist in the same issue.
|
||||
|
||||
## Removing tasks from a tasklist
|
||||
|
||||
You can remove issues, pull requests, and draft tasks from your tasklist. Issues and pull requests removed from a tasklist are not removed from the repository. Draft tasks are permanently deleted.
|
||||
|
||||
1. Place your cursor over the task you want to remove and next to the task, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. In the menu, click **Remove**.
|
||||
@@ -1,168 +0,0 @@
|
||||
---
|
||||
title: 'Quickstart for tasklists'
|
||||
shortTitle: 'Quickstart for tasklists'
|
||||
intro: 'Follow this guide to learn how to create and modify tasklists in the UI and with Markdown.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: quick_start
|
||||
topics:
|
||||
- Issues
|
||||
---
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide demonstrates how to use tasklists to split up a larger piece of work into multiple tasklists and multiple subtasks. You will learn how to create a tasklist using the UI, how to create a tasklist using Markdown, how to make changes to a tasklist, and how to integrate your new tasklists with a project.
|
||||
|
||||
To help demonstrate how tasklists can be used to divide work into smaller subtasks, this guide will follow a scenario where we need to create a landing page for a new feature. Feel free to follow this guide but incorporate your own scenario.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
As you follow this guide, you will create several issues in a repository. You will need a repository that you are able to create issues in.
|
||||
|
||||
## Creating an issue to track the work of adding a new landing page
|
||||
|
||||
In this step, we will create the parent issue to track the subtasks required to publish the new landing page.
|
||||
|
||||
1. Navigate to the repository where you want to track the work.
|
||||
1. Create a new blank issue with the title "Tracking issue for landing page." For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/creating-an-issue)."
|
||||
|
||||
## Creating the first tasklist
|
||||
|
||||
Tasklists are added to the opening comment of an issue (the issue description). Issues can contain multiple tasklists with different titles. This is a great way to categorize your subtasks.
|
||||
|
||||
1. Go to the issue you just created. If you have not already done so, press **Submit new issue**.
|
||||
1. At the bottom of the issue description, click {% octicon "plus" aria-hidden="true" %} **Add tasklist**.
|
||||
|
||||
|
||||
|
||||
This will insert an empty tasklist into your issue.
|
||||
|
||||
## Adding draft tasks
|
||||
|
||||
Draft tasks are text items that are added to your tasklist. Draft tasks appear in your tasklist with a checkbox. You can use draft tasks to quickly sketch out the requirements and subtasks for your project and, optionally, later convert them into issues.
|
||||
|
||||
1. If the text field is not already focused, click **Add item to Tasks**.
|
||||
|
||||
|
||||
|
||||
1. Add some draft tasks to sketch out this work. Type your draft task and then press <kbd>Enter</kbd> after each one.
|
||||
|
||||
For our example landing page scenario, you can add:
|
||||
* "Design new landing page"
|
||||
* "Create content for landing page"
|
||||
* "Translate content into supported languages"
|
||||
|
||||
## Converting a draft task into an issue
|
||||
|
||||
You can convert your draft tasks into issues. You can convert draft tasks when you're ready to start work on a particular task. The issues are created in the same repository you have used for your tracking issue.
|
||||
|
||||
1. Next to the "Design new landing page" draft task, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. In the menu, click **Convert to issue**.
|
||||
|
||||
## Assigning yourself to the new issue
|
||||
|
||||
You can now assign yourself to the new issue without leaving your tasklist.
|
||||
|
||||
1. Next to the "Design new landing page" issue in your tasklist, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. In the context menu, click **Set assignees**.
|
||||
1. In the list of people, select yourself.
|
||||
|
||||
You can also use this context menu to set labels and add an issue to a project.
|
||||
|
||||
## Renaming a tasklist
|
||||
|
||||
You can change the title of a tasklist to better represent the tasks it is tracking. This is particularly useful when you have multiple tasklists in the same issue and want to segment your tasks.
|
||||
|
||||
1. In the top-right of your tasklist, click {% octicon "kebab-horizontal" aria-label="tracking block item menu" %}.
|
||||
|
||||
|
||||
|
||||
1. In the menu, click **Rename**.
|
||||
1. Type a new title for your tasklist and press <kbd>Enter</kbd>.
|
||||
|
||||
For our example landing page scenario, you could rename this tasklist to "Landing page content."
|
||||
|
||||
## Creating a second tasklist using Markdown
|
||||
|
||||
You can create multiple tasklists in a single issue. Each tasklist has its own tasks and title. You can add tasklists using the **Add tasklist** button or by entering Markdown when you edit the issue.
|
||||
|
||||
1. At the top of the issue description (the opening comment), click {% octicon "kebab-horizontal" aria-label="Show options" %}.
|
||||
|
||||
|
||||
|
||||
1. In the menu, click **Edit**.
|
||||
1. In the issue description, below your first tasklist, add the Markdown below:
|
||||
|
||||
````markdown copy
|
||||
```[tasklist]
|
||||
### Tasks
|
||||
- [ ] Draft task
|
||||
```
|
||||
````
|
||||
|
||||
1. To change the title of this tasklist, type a new title after `### `. For example, change `### Tasks` to `### Backend changes`.
|
||||
|
||||
In the next two sections, we will make further changes to the Markdown before saving the comment.
|
||||
|
||||
## Adding draft tasks using Markdown
|
||||
|
||||
You can quickly add new draft tasks by just typing them directly into your tasklist using Markdown.
|
||||
|
||||
1. Add new draft tasks by create a new line after the last task, typing `- [ ] ` and your new task. For example, `- [ ] Sign-up form`.
|
||||
1. Edit an existing draft task by modifying the text after `- [ ]`. For example, change `- [ ] Draft task` to `- [ ] Database schema`.
|
||||
|
||||
## Adding existing issues using Markdown
|
||||
|
||||
You can also track existing issues by adding them to your tasklist. You can add existing issues using Markdown or in the UI by pasting the issue URL. You can add issues and pull requests from any repository you have access to.
|
||||
|
||||
1. Start typing `- [ ] ` on a new line and then paste the full URL of an issue. For example, `- [ ] https://github.com/octo-org/octo-repo/issues/45`
|
||||
1. Click **Update comment**.
|
||||
|
||||
|
||||
|
||||
You will see your new second tasklist displayed beneath your first tasklist.
|
||||
|
||||
## Tracking progress
|
||||
|
||||
Tasklists help you quickly see the status and progress of the tasks you have chosen to track.
|
||||
|
||||
1. To the left of one of your draft tasks, select the checkbox to mark that task as done.
|
||||
1. Click on the issue that you previously converted from a draft.
|
||||
1. In the converted issue, at the bottom of the page, click **Close issue**.
|
||||
|
||||
When you return to your tasklist and refresh the page, you can see that the issue you just closed now has an icon indicating that is closed. At the top of the issue, below the title, the progress is indicated as "2 of 6 tasks."
|
||||
|
||||
|
||||
|
||||
## Integrate with a project
|
||||
|
||||
The relationships you build in your tasklists are available in your projects. You can quickly see the progress made in each issue, browse through the subtasks, and setup views that use your tasklists.
|
||||
|
||||
1. Navigate to a project that's owned by the same user or organization account that you have used for your tasklist and issues. If you don't have a project available, you can create one. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)."
|
||||
1. Create a new view in your project using the table layout. For more information on views, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
|
||||
1. Add one of the issues from your tasklists to your project. For more information on adding items to projects, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)."
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. In the menu, click **Group by** and then select **Tracked by**. This creates a view where your issues are grouped by the issue that is tracking them.
|
||||
|
||||
Issues and pull requests are not automatically added to a project when they are added to a tasklist. When you group a view by the "Tracked by" field, {% data variables.product.product_name %} will prompt you add other issues associated with the tasklist.
|
||||
|
||||
1. If there are issues in your tasklists that are not part of your project, you can click **1 item not in this project** below the group.
|
||||
|
||||
|
||||
|
||||
1. In the list of issues, click on the issue you want to add. If you have multiple issues, you can choose to add all of them.
|
||||
|
||||
## Conclusion
|
||||
|
||||
After following this guide, you have created a tracking issue with two tasklists, made changes to those tasklists in the UI and directly with Markdown, converted a draft task into an issue, and integrated your tasklist data with a project.
|
||||
|
||||
To learn more about managing the items in your tasklist, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist)." For more information on integrating tasklists with your projects, see "[AUTOTITLE](/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists)."
|
||||
@@ -1,60 +0,0 @@
|
||||
---
|
||||
title: 'Using projects and tasklists'
|
||||
intro: 'When issues in your project are tracked by tasklists or contain tasklists, you can use them to create views and filters. {% ifversion projects-v2-tasklists-without-breadcrumbs %}{% else %}You can also browse any linked issues when you display the details for an issue.{% endif %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: overview
|
||||
topics:
|
||||
- Issues
|
||||
---
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
When you add tasklists to your issues and view those issues in your projects, you can use the relationships that you defined in your tasklists to customize views, filter items, and navigate through your issues and pull requests.
|
||||
|
||||
When you add an issue with a tasklist to a project, the issues and pull requests in the tasklist are not automatically added to the project. To use the "tracks" and "tracked-by" fields, you will need to add all the issues and pull requests that comprise your tasklist to the project. Consider using the auto-add workflow to automatically add issues to your project. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically)."
|
||||
|
||||
When you group a view by "Tracked by", and some tracked issues and pull requests are not part of the project, {% data variables.product.product_name %} will include a note beneath each group with the option to add those missing issues and pull requests.
|
||||
|
||||
## Using the "tracks" field
|
||||
|
||||
The "tracks" field shows the number of the issues and pull requests included each issue's tasklists. For more information about this field, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields)."
|
||||
|
||||
## Using the "tracked by" field
|
||||
|
||||
The "tracked by" field shows the issues with tasklists currently tracking your project's issues. The "tracked by" field can also be used to group and filter views. You can use the filter below to only show issues that are tracked by issue you have specified:
|
||||
|
||||
```text
|
||||
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
```
|
||||
|
||||
For example, `tracked-by:"octocat/game#4"` will show any issues in the project that are tracked by a tasklist in issue #4 in the `octocat/game` repository.
|
||||
|
||||
You can also group a table layout by the "tracked-by" field. This view configuration results in a list of the issues found in tasklists, clearly grouped by the issue they're associated with, which is shown in the header for each group.
|
||||
|
||||
You can also combine filters and grouping by filtering your project for just the issues you want to use, and then grouping with the "tracked-by" field. The example below shows how to filter a view by multiple issues:
|
||||
|
||||
```text
|
||||
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>","<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
```
|
||||
|
||||
For more information about this field, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields)."
|
||||
|
||||
{% ifversion projects-v2-tasklists-without-breadcrumbs %}{% else %}
|
||||
|
||||
## Navigating issue hierarchy with a breadcrumb menu
|
||||
|
||||
When the issues added to your project are either tracked by tasklists or contain tasklists, the project side-panel allows you to quickly move through the associated issues. Clicking on either the issues in the tasklists or the breadcrumb menu will open that issue in the side-panel.
|
||||
|
||||
1. In your project, click on an issue that either contains a tasklist or is tracked by a tasklist in another issue.
|
||||
1. In the issue that opens in the side-bar, you can navigate through the associated issues.
|
||||
* To navigate down the issue hierarchy, and view the tasks that comprise the current issue, click on issues in the tasklist.
|
||||
|
||||
|
||||
|
||||
* To navigate up the issue hierarchy, and view the issues that include the current issue as a task, click on an issue number in the breadcrumb menu.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
@@ -126,18 +126,6 @@ You can filter closed items by their close reason.
|
||||
| | **reason:"not planned"** will show closed items with the "not planned" reason.
|
||||
| | **reason:reopened** will show items that have been reopened after previously being closed.
|
||||
|
||||
{% ifversion projects-v2-tasklists %}
|
||||
|
||||
## Filtering by the tracked-by field
|
||||
|
||||
You can filter for issues that are tracked by another issue in a tasklist. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/about-tasklists)."
|
||||
|
||||
| Qualifier | Example
|
||||
| ---------- | -------------
|
||||
| <code>tracked-by:"<em>OWNER</em>/<em>REPO</em>#<em>ISSUE NUMBER</em>"</code> | **tracked-by:"octocat/game#11"** will show any issue tracked by a tasklist in issue #11 of the `octocat/game` repository.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Filtering for when an item was last updated
|
||||
|
||||
You can use the `{number}days` syntax to filter for when items were last updated.
|
||||
|
||||
@@ -41,18 +41,6 @@ There are a number of ways you can add automation to your project. Built-in work
|
||||
|
||||
You can also use the GraphQL API and {% data variables.product.prodname_actions %} to take even greater control of your project. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)."
|
||||
|
||||
{% ifversion projects-v2-tasklists %}
|
||||
|
||||
### Exploring the relationships between issues
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
You can use tasklists to build hierarchies of issues, dividing your issues into smaller subtasks, and creating new relationships between your issues. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/about-tasklists)."
|
||||
|
||||
These relationships are displayed on the issue, as well as the Tracked by and Tracks fields in your projects. You can filter by issues which are tracked by another issue, and you can also group your table views by the Tracked by field to show all parent issues with a list of their subtasks.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Viewing your project from different perspectives
|
||||
|
||||
Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options.
|
||||
|
||||
@@ -19,7 +19,7 @@ You can use {% data variables.product.prodname_projects_v2 %} to manage your wor
|
||||
|
||||
Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review.
|
||||
|
||||
To track how smaller issues fit into the larger goal, use task lists, milestones, or labels. For more information, see {% ifversion projects-v2-tasklists %}"[AUTOTITLE](/issues/tracking-your-work-with-issues/about-tasklists)"{% endif %}{% ifversion ghes %}"[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists)"{% endif %}, "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones)", and "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels)."
|
||||
To track how smaller issues fit into the larger goal, milestones, or labels. For more information, see "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones)" and "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/managing-labels)."
|
||||
|
||||
## Communicate
|
||||
|
||||
|
||||
@@ -1,48 +0,0 @@
|
||||
---
|
||||
title: About Tracks and Tracked by fields
|
||||
shortTitle: About Tracks and Tracked by fields
|
||||
intro: You can view the subtasks of the issues in your projects.
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Tasklists and the tracks and tracked by fields for Projects are currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can enable the "Tracks" and "Tracked by" fields on your projects to see the relationships between your issues as you add subtasks in tasklists. For more information about creating issue hierarchies in tasklists, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/about-tasklists)."
|
||||
|
||||
The "Tracked by" field can be used to group items, creating a view that clearly shows the subtasks of each issue and the work required to complete them. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view#grouping-by-field-values-in-table-layout)."
|
||||
|
||||
You can also filter by the "Tracked by" field to display only items that are tracked by specific issues. You can start by typing "tracked-by" and select an issue from the list. Or, if you know the repository and issue number, you can type the following filter in full:
|
||||
|
||||
```text
|
||||
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
```
|
||||
|
||||
To use the filter, replace `<OWNER>` with the repository owner, `<REPO>` with the repository name, and `<ISSUE NUMBER>` with the issue number. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
|
||||
|
||||
## Enabling the Tracked by field
|
||||
|
||||
You can enable the "Tracked by" field to see which issues are tracking an item in your project.
|
||||
|
||||
1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
|
||||
|
||||
1. Under "Hidden fields", click **Tracked by**.
|
||||
|
||||
## Enabling the Tracks field
|
||||
|
||||
You can enable the "Tracks" field to see what other issues an item in your project is tracking.
|
||||
|
||||
1. In table view, in the rightmost field header, click {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
|
||||
|
||||
1. Under "Hidden fields", click **Tracks**.
|
||||
@@ -12,11 +12,11 @@ children:
|
||||
- /about-date-fields
|
||||
- /about-single-select-fields
|
||||
- /about-iteration-fields
|
||||
- /about-tracks-and-tracked-by-fields
|
||||
- /renaming-custom-fields
|
||||
- /deleting-custom-fields
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /issues/planning-and-tracking-with-projects/understanding-field-types
|
||||
- /issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields
|
||||
---
|
||||
|
||||
|
||||
@@ -10,6 +10,8 @@ topics:
|
||||
- Issues
|
||||
- Project management
|
||||
shortTitle: Close an issue
|
||||
redirect_from:
|
||||
- /issues/tracking-your-work-with-issues/closing-an-issue
|
||||
---
|
||||
|
||||
{% note %}
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /articles/deleting-an-issue
|
||||
- /github/managing-your-work-on-github/deleting-an-issue
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/deleting-an-issue
|
||||
- /issues/tracking-your-work-with-issues/deleting-an-issue
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: Administering issues
|
||||
intro: 'Learn about performing administrative tasks on issues in your repositories.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Issues
|
||||
children:
|
||||
- /pinning-an-issue-to-your-repository
|
||||
- /marking-issues-or-pull-requests-as-a-duplicate
|
||||
- /transferring-an-issue-to-another-repository
|
||||
- /closing-an-issue
|
||||
- /deleting-an-issue
|
||||
---
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /articles/about-duplicate-issues-and-pull-requests
|
||||
- /github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/managing-issues/marking-issues-or-pull-requests-as-a-duplicate
|
||||
- /issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -7,6 +7,7 @@ redirect_from:
|
||||
- /articles/pinning-an-issue-to-your-repository
|
||||
- /github/managing-your-work-on-github/pinning-an-issue-to-your-repository
|
||||
- /issues/tracking-your-work-with-issues/managing-issues/pinning-an-issue-to-your-repository
|
||||
- /issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /articles/transferring-an-issue-to-another-repository
|
||||
- /github/managing-your-work-on-github/transferring-an-issue-to-another-repository
|
||||
- /issues/tracking-your-work-with-issues/managing-issues/transferring-an-issue-to-another-repository
|
||||
- /issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
title: Configuring issues
|
||||
intro: 'Learn how to configure your repository to start using issues.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Issues
|
||||
children:
|
||||
- /quickstart
|
||||
- /planning-and-tracking-work-for-your-team-or-project
|
||||
---
|
||||
@@ -9,6 +9,8 @@ type: overview
|
||||
topics:
|
||||
- Project management
|
||||
- Projects
|
||||
redirect_from:
|
||||
- /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
|
||||
---
|
||||
## Introduction
|
||||
|
||||
@@ -10,6 +10,8 @@ type: quick_start
|
||||
topics:
|
||||
- Issues
|
||||
- Project management
|
||||
redirect_from:
|
||||
- /issues/tracking-your-work-with-issues/quickstart
|
||||
---
|
||||
|
||||
## Introduction
|
||||
@@ -10,21 +10,18 @@ topics:
|
||||
- Issues
|
||||
children:
|
||||
- /about-issues
|
||||
- /quickstart
|
||||
- /creating-an-issue
|
||||
- /about-slash-commands
|
||||
- /linking-a-pull-request-to-an-issue
|
||||
- /creating-a-branch-for-an-issue
|
||||
- /assigning-issues-and-pull-requests-to-other-github-users
|
||||
- /viewing-all-of-your-issues-and-pull-requests
|
||||
- /filtering-and-searching-issues-and-pull-requests
|
||||
- /marking-issues-or-pull-requests-as-a-duplicate
|
||||
- /pinning-an-issue-to-your-repository
|
||||
- /transferring-an-issue-to-another-repository
|
||||
- /closing-an-issue
|
||||
- /deleting-an-issue
|
||||
- /planning-and-tracking-work-for-your-team-or-project
|
||||
- /configuring-issues
|
||||
- /using-issues
|
||||
- /administering-issues
|
||||
redirect_from:
|
||||
- /issues/tracking-your-work-with-issues/creating-issues
|
||||
- /issues/tracking-your-work-with-issues/managing-issues
|
||||
- /early-access/issues/about-tasklists
|
||||
- /issues/tracking-your-work-with-issues/about-tasklists
|
||||
- /issues/managing-your-tasks-with-tasklists/about-tasklists
|
||||
- /issues/managing-your-tasks-with-tasklists/creating-a-tasklist
|
||||
- /issues/managing-your-tasks-with-tasklists
|
||||
- /issues/managing-your-tasks-with-tasklists/managing-tasks-in-a-tasklist
|
||||
- /issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists
|
||||
- /issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists
|
||||
---
|
||||
|
||||
@@ -5,6 +5,7 @@ versions:
|
||||
feature: slash-commands
|
||||
redirect_from:
|
||||
- /early-access/issues/about-slash-commands
|
||||
- /issues/tracking-your-work-with-issues/about-slash-commands
|
||||
---
|
||||
|
||||
{% note %}
|
||||
@@ -29,5 +30,4 @@ You can use slash commands by typing the command in a comment field, then follow
|
||||
| `/details` | Inserts a collapsible detail area. You choose the title and content.
|
||||
| `/saved-replies` | Inserts a saved reply. You choose from the saved replies for your user account. If you add `%cursor%` to your saved reply, the slash command will place the cursor in that location.
|
||||
| `/table` | Inserts a Markdown table. You choose the number of columns and rows.
|
||||
| `/tasklist` | Inserts a tasklist. This slash command only works in an issue description. {% note %} **Note:** tasklists are currently in private beta and may not be available to all users. For more information, see "[AUTOTITLE](/issues/tracking-your-work-with-issues/about-tasklists)." {% endnote %}
|
||||
| `/template` | Shows all of the templates in the repository. You choose the template to insert. This slash command will work for issue templates and a pull request template.
|
||||
@@ -7,6 +7,7 @@ redirect_from:
|
||||
- /articles/assigning-issues-and-pull-requests-to-other-github-users
|
||||
- /github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users
|
||||
- /issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users
|
||||
- /issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -9,6 +9,8 @@ allowTitleToDifferFromFilename: true
|
||||
topics:
|
||||
- Issues
|
||||
shortTitle: Create branch for issue
|
||||
redirect_from:
|
||||
- /issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue
|
||||
---
|
||||
|
||||
{% note %}
|
||||
@@ -18,6 +18,7 @@ redirect_from:
|
||||
- /articles/about-automation-for-issues-and-pull-requests-with-query-parameters
|
||||
- /github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue
|
||||
- /issues/tracking-your-work-with-issues/creating-an-issue
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -33,6 +33,7 @@ redirect_from:
|
||||
- /github/administering-a-repository/finding-information-in-a-repository/sorting-issues-and-pull-requests
|
||||
- /github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests
|
||||
- /github/administering-a-repository/finding-information-in-a-repository/sharing-filters
|
||||
- /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
title: Using issues
|
||||
intro: 'Learn about using issues in your repositories.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Issues
|
||||
children:
|
||||
- /creating-an-issue
|
||||
- /assigning-issues-and-pull-requests-to-other-github-users
|
||||
- /viewing-all-of-your-issues-and-pull-requests
|
||||
- /filtering-and-searching-issues-and-pull-requests
|
||||
- /creating-a-branch-for-an-issue
|
||||
- /linking-a-pull-request-to-an-issue
|
||||
- /about-slash-commands
|
||||
---
|
||||
@@ -9,6 +9,7 @@ redirect_from:
|
||||
- /github/managing-your-work-on-github/closing-issues-using-keywords
|
||||
- /github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue
|
||||
- /issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /articles/viewing-all-of-your-issues-and-pull-requests
|
||||
- /github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/managing-issues/viewing-all-of-your-issues-and-pull-requests
|
||||
- /issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
Reference in New Issue
Block a user