text stringlengths 12 91.7k | metadata dict |
|---|---|
You can customize your notifications by subscribing to activity that is relevant to your Microsoft Teams channel, and unsubscribing from activity that is less helpful to your project.
Notifications enabled by default
The following notifications are enabled by default, but you can disable any of them using the @GitHub ... | {
"source": "github-docs/integrations/how-tos/teams/customize-notifications.md",
"title": "Customizing notifications for {% data variables.product.github %} in Teams"
} |
FeatureDescription
------------------
reviewsPull request reviews.
workflows workflow runs and approval notifications.
branchesBranch creation and deletion.
discussionsDiscussions created or answered.
+label:"your label"Filter issues, pull requests, and comments based on their labels.
You can subscribe or unsubscribe f... | {
"source": "github-docs/integrations/how-tos/teams/customize-notifications.md",
"title": "Customizing notifications for {% data variables.product.github %} in Teams"
} |
Example configurationDescription
------------------
@GitHub Notifications subscribe owner/repo commitsReceive commit notifications for the default branch.
@GitHub Notifications subscribe owner/repo commits:mainOnly receive commit notifications for the main branch.
@GitHub Notifications subscribe owner/repo commits:feat... | {
"source": "github-docs/integrations/how-tos/teams/customize-notifications.md",
"title": "Customizing notifications for {% data variables.product.github %} in Teams"
} |
Branches
Creating label filters
To create a label filter, use the following command format:
@GitHub Notifications subscribe [owner/repo] +label:"your label"
This creates a required-label filter with the value your label. Incoming events that support filters are discarded unless they have that label.
Updating label fi... | {
"source": "github-docs/integrations/how-tos/teams/customize-notifications.md",
"title": "Customizing notifications for {% data variables.product.github %} in Teams"
} |
FilterDescription
------------------
nameFilter by the name of the workflow.
actorFilter by the user who triggered the workflow.
branchFilter by the branch the workflow is running on. In cases where the pullrequest event is included, the branch will be the target branch the pull request is created for.
eventFilter by t... | {
"source": "github-docs/integrations/how-tos/teams/customize-notifications.md",
"title": "Customizing notifications for {% data variables.product.github %} in Teams"
} |
About the integration for Teams
The integration for Microsoft Teams gives you and your teams visibility into your projects directly in Teams channels. You can triage issues, collaborate on pull requests, and keep track of changes without leaving Teams.
With the integration for Teams, you can:
Get notifications in... | {
"source": "github-docs/integrations/how-tos/teams/integrate-github-with-teams.md",
"title": "Integrating {% data variables.product.github %} with Teams"
} |
You can schedule reminders for pending pull request reviews in Microsoft Teams channels or in the personal app. Reminders are available for organizations, not personal accounts.
Scheduling reminders in a channel
1. In a Teams channel, run @GitHub Notifications schedule ORGANIZATION.
1. Select Create new reminder.
1. ... | {
"source": "github-docs/integrations/how-tos/teams/schedule-reminders.md",
"title": "Scheduling pull request reminders in Teams"
} |
The integration for Microsoft Teams lets you connect your account to the app in Teams. Once connected, you can subscribe to notifications, run commands, and collaborate on issues and pull requests directly within Teams.
Connecting your account to the app in Teams
[!NOTE] Before you can connect your accounts, an a... | {
"source": "github-docs/integrations/how-tos/teams/use-github-in-teams.md",
"title": "Using {% data variables.product.github %} in Teams"
} |
CommandDescription
------
@GitHub Notifications subscribe owner/repoSubscribes the channel to notifications for the specified repository.
@GitHub Notifications unsubscribe owner/repoUnsubscribes the channel from notifications for the specified repository.
@GitHub Notifications subscribe listLists all repositories the c... | {
"source": "github-docs/integrations/how-tos/teams/use-github-in-teams.md",
"title": "Using {% data variables.product.github %} in Teams"
} |
By granting the app access to your Slack workspace, you are providing necessary authorizations to your account and your Slack workspace. These permissions enable the app to perform its functions and provide you with a seamless experience when using GitHub in Slack.
Slack permissions
When you install the app in your... | {
"source": "github-docs/integrations/reference/slack-permissions.md",
"title": "Permissions for GitHub in Slack"
} |
Use these commands in a Microsoft Teams channel by prefixing them with @GitHub Notifications. In the personal app, omit the prefix.
CommandDescription
------
@GitHub Notifications helpDisplay help documentation.
@GitHub Notifications signinConnect your account.
@GitHub Notifications subscribe owner/repoSubscribe a ch... | {
"source": "github-docs/integrations/reference/teams-command-reference.md",
"title": "Command reference for the {% data variables.product.github %} integration in Teams"
} |
By granting the app access to your Microsoft Teams workspace, you are providing necessary authorizations to your account and your Teams workspace. These permissions enable the app to perform its functions and provide you with a seamless experience when using in Teams.
Teams permissions
When you install the app in ... | {
"source": "github-docs/integrations/reference/teams-permissions.md",
"title": "Permissions for {% data variables.product.github %} in Teams"
} |
Creating issues with the integration in Slack
With the integration in Slack, you can create issues in any repository that you have access to directly from Slack. This enables you to quickly capture and track tasks, bugs, or feature requests as they arise during conversations in Slack. You must be connected to your a... | {
"source": "github-docs/integrations/tutorials/slack/create-issues.md",
"title": "Creating issues with the GitHub integration in Slack"
} |
Managing issues in Slack
With the integration in Slack, you can comment on, edit, and close issues directly from Slack. You must be connected to the app in Slack and have the necessary permissions to manage issues in the relevant repository.
1. In Slack, under the preview of the issue you want to manage, select the a... | {
"source": "github-docs/integrations/tutorials/slack/manage-issues.md",
"title": "Managing issues with the GitHub integration in Slack"
} |
Creating issues with the integration in Teams
With the integration in Microsoft Teams, you can create issues in any repository that you have access to directly from Teams. This enables you to quickly capture and track tasks, bugs, or feature requests as they arise during conversations in Teams. You must be signed in ... | {
"source": "github-docs/integrations/tutorials/teams/create-issues.md",
"title": "Creating issues with the GitHub integration in Teams"
} |
Managing issues in Teams
With the integration in Microsoft Teams, you can comment on, close, and reopen issues directly from Teams. You must be signed in to in Teams and have the necessary permissions to manage issues in the relevant repository.
1. In Teams, under the preview of the issue you want to manage, select t... | {
"source": "github-docs/integrations/tutorials/teams/manage-issues.md",
"title": "Managing issues with the GitHub integration in Teams"
} |
About automatically adding items
You can configure your project's built-in workflows to automatically add new items as they are created or updated in a repository. You can define a filter to only add items that meet your criteria. You can also create multiple auto-add workflows, each workflow can have a unique filter ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/automating-your-project/adding-items-automatically.md",
"title": "Adding items automatically"
} |
About automatically archiving items
You can configure your project's built-in workflows to automatically archive items. Archiving items helps you improve focus by removing old items from your project views. An archived item retains all of its custom field data and can be viewed or restored from the archive page.
You ca... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md",
"title": "Archiving items automatically"
} |
workflows
This article demonstrates how to use the GraphQL API and to add a pull request to an organization project. In the example workflows, when the pull request is marked as "ready for review", a new task is added to the project with a "Status" field set to "Todo", and the current date is added to a custom "Date p... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md",
"title": "Automating {% data variables.product.prodname_projects_v2 %} using Actions"
} |
This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a workflow, see AUTOTITLE. For a full list of the available data types, see AUTOTITLE.
Authentication
In all of the following curl command examples, replace TOKEN with a token that has the read:p... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md",
"title": "Using the API to manage {% data variables.product.prodname_projects_v2 %}"
} |
includes built-in workflows that you can use to update the Status of items based on certain events. For example, you can automatically set the status to Todo when an item is added to your project, close issues when the issue's status in your project is changed, or set the status to Done when an issue is closed.
When yo... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md",
"title": "Using the built-in automations"
} |
About copying projects
You can copy an existing project and use it as a template to save time configuring your views and custom fields.
When you copy a project, the new project will contain the same . The new project will not contain the original project's items, collaborators, or team and repository links.
Copying an... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/creating-projects/copying-an-existing-project.md",
"title": "Copying an existing {% data variables.projects.project_v2 %}"
} |
are an adaptable collection of items that stay up-to-date with data. Your projects can track issues, pull requests, and ideas that you note down. You can add custom fields and create views for specific purposes.
You can also choose to use an existing project as a template and copy the views and custom fields to a new ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md",
"title": "Creating a {% data variables.projects.project_v2 %}"
} |
About the table layout
For more information, see AUTOTITLE.
About the board layout
For more information, see AUTOTITLE.
About the roadmap layout
For more information, see AUTOTITLE.
Changing the project layout
You can set each view in your project to a different layout.
1. Under "Layout", click either Table, Boar... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view.md",
"title": "Changing the layout of a view"
} |
About the board layout
For more information about changing a view to use the board layout, see AUTOTITLE.
Setting a limit on the number of items in a column
You can set a limit for the number of cards in a particular column in a board layout. Setting a limit does not restrict anyone from adding cards that would exceed... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md",
"title": "Customizing the board layout"
} |
About the roadmap layout
For more information about changing a view to use the roadmap layout, see AUTOTITLE.
Setting the start and target date fields
You can set the date or iteration fields that your roadmap will use to position items. When you set a view to a roadmap layout, will attempt to use existing date and i... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md",
"title": "Customizing the roadmap layout"
} |
About the table layout
For more information about changing a view to use the table layout, see AUTOTITLE.
Showing and hiding fields
You can show or hide a specific field.
You can also hide individual fields using the field headers.
1. Next to the field you want to hide, click .
!Screenshot showing a field header. T... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md",
"title": "Customizing the table layout"
} |
You can customize which items appear in your views using filters for item metadata, such as assignees and the labels applied to issues, and by the fields in your project. You can combine filters and save them as views. For more information, see AUTOTITLE.
To filter a view, click and start typing the fields and values ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md",
"title": "Filtering {% data variables.projects.projects_v2 %}"
} |
Creating a project view
Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project.
For example, you can have:
A view that shows all items not yet started (filter on "Status").
A view that shows the workload for each team (group by a custom "Team... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md",
"title": "Managing your views"
} |
Browsing all of your projects
You can browse all of your projects, regardless of where they are located. You can see the projects you have recently viewed and the projects you have created, and apply your own filters.
1. In the top left of any page, click to open the global navigation menu.
1. In the menu, click Proj... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/finding-your-projects.md",
"title": "Finding your {% data variables.projects.projects_v2 %}"
} |
A project is an adaptable collection of items that you can view as a table, a kanban board, or a roadmap and that stays up-to-date with data. Your projects can track issues, pull requests, and ideas that you note down.
You can create and customize multiple views by filtering, sorting, and grouping issues and pull requ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/index.md",
"title": "Planning and tracking with {% data variables.product.prodname_projects_v2 %}"
} |
About
A project is an adaptable table, board, and roadmap that integrates with your issues and pull requests on to help you plan and track your work effectively at the user or organization level. You can create and customize multiple views by filtering, sorting, slicing, and grouping your issues and pull requests to ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md",
"title": "About {% data variables.product.prodname_projects_v2 %}"
} |
You can use to manage your work on , where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about , see AUTOTITLE.
Communicate across your issues and pull requests
Issues and pull requests include built-in features to let you easily communi... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md",
"title": "Best practices for {% data variables.product.prodname_projects_v2 %}"
} |
Introduction
This guide demonstrates how to use to plan and track work. In this guide, you will create a new project, customize views, and add custom fields to manage a team backlog, iteration planning, and a team roadmap to communicate priorities and progress with your collaborators. You'll also set up built-in workf... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md",
"title": "Quickstart for {% data variables.product.prodname_projects_v2 %}"
} |
[!NOTE]
A project can contain a maximum of items across both active views and the archive page items and archived items. To learn more about automatically archiving items when they meet specific criteria, see AUTOTITLE.
Adding issues and pull requests to a project
You have several options for adding issues and pul... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md",
"title": "Adding items to your {% data variables.projects.project_v2 %}"
} |
[!NOTE]
A project can contain a maximum of items across both active views and the archive page items and archived items.
Archiving items
You can archive an item to keep the context about the item in the project but remove it from the project views. You can also configure your project's built-in workflows to automa... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md",
"title": "Archiving items from your {% data variables.projects.project_v2 %}"
} |
Converting draft issues in table layout
1. Click the on the draft issue that you want to convert.
!Screenshot of items in the table layout. The item context button is highlighted with an orange outline.
1. Select Convert to issue.
1. Select the repository that you want to add the issue to.
Converting draft issues ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md",
"title": "Converting draft issues to issues"
} |
Copying and pasting cells in a table
You can copy the contents of one cell and paste the contents into multiple other cells in the same field.
1. Navigate to a project view that is using the table layout.
1. Select the cell that you would like to copy.
!Screenshot showing two columns on a table layout. One cell is s... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-items-in-your-project/editing-items-in-your-project.md",
"title": "Editing items in your {% data variables.projects.project_v2 %}"
} |
Linking a repository to your project
You can list relevant projects in a repository. You can only list projects that are owned by the same user or organization that owns the repository.
In order for repository members to see a project listed in a repository, they must have visibility for the project. For more informati... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md",
"title": "Adding your {% data variables.projects.project_v2 %} to a repository"
} |
About adding projects to teams
You can add projects to your team to give the whole team collaborator access to their projects. When you add a project to a team, that project is listed on the team's projects page, making it easier for members to identify which projects a particular team uses.
Teams are granted read perm... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md",
"title": "Adding your {% data variables.projects.project_v2 %} to a team"
} |
Deleting a project
You can delete a project to permanently remove it.
1. In the "Danger zone" section, next to "Delete project," click Delete this project.
1. Read the warnings, then type the name of your project into the text box.
1. Click I understand the consequences, delete this project.
Closing a project
You can ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md",
"title": "Closing and deleting your {% data variables.projects.projects_v2 %}"
} |
You can download a view as a .tsv (tab-separated) file.
1. On , navigate to the main page of your repository.
1. Click Projects.
!Screenshot showing a repository's tabs. The "Projects" tab is highlighted with an orange outline.
1. Click Export view data. | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/exporting-your-projects-data.md",
"title": "Exporting your {% data variables.projects.project_v2 %} data"
} |
About project access
Admins of organization-level projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators.
Admins of user-level projects can invite individual collaborators and manage their access.
Project admins can also control the visibili... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md",
"title": "Managing access to your {% data variables.projects.projects_v2 %}"
} |
About templates
You can create a template, or set a project as a template, to share a pre-configured project with other people in your organization which they can then use as the base for their projects.
The projects you mark as templates are shown in the "Create a project" dialog when anyone creates a project in your ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization.md",
"title": "Managing {% data variables.projects.project_v2 %} templates in your organization"
} |
About project visibility
Project visibility can be set to private, internal when using an , or public if your enterprise does not use public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project. For internal pr... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md",
"title": "Managing visibility of your {% data variables.projects.projects_v2 %}"
} |
About status updates
You can keep your team up to date and share high-level overviews, which people can use to determine the status of your project. You can set a status, such as "On track" or "At risk", to allow people to quickly determine the current state of the project. You can also set start dates and target dates... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/sharing-project-updates.md",
"title": "Sharing {% data variables.projects.project_v2 %} updates"
} |
You can filter for date values using the YYYY-MM-DD format, for example: date:2022-07-01. You can also use operators, such as , =, <, <=, and ... For example, date:2022-07-01 and date:2022-07-01..2022-07-31. You can also provide @today to represent the current day in your filter. For more information, see AUTOTITLE.
If... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md",
"title": "About date fields"
} |
Issue fields are organization-level fields that provide consistent, typed metadata across all repositories. Unlike project custom fields, issue fields are defined once at the organization level and are available on every issue and in every project across the organization. For more information on creating and managing i... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-issue-fields.md",
"title": "About issue fields in projects"
} |
You can create an iteration field to associate items with specific repeating blocks of time. Iterations can be set to any length of time, can include breaks, and can be individually edited to modify name and date range. With projects, you can group by iteration to visualize the balance of upcoming work, use filters to ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md",
"title": "About iteration fields"
} |
If your organization uses sub-issues, you can enable the "Parent issue" and "Sub-issue progress" fields on your projects to see the relationships between your issues and the progress made on those issues.
The "Parent issue" field can be used to group items, allowing you to create views that break down your work using t... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-parent-issue-and-sub-issue-progress-fields.md",
"title": "About parent issue and sub-issue progress fields"
} |
You can enable the "Linked pull requests" and "Reviewers" fields on your projects to see information about a pull request, making a project the way to plan and track your issues, pull request, and code.
Enabling the Linked pull requests field
You can enable the "Linked pull requests" field to see the pull request link... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-pull-request-fields.md",
"title": "About pull request fields"
} |
You can filter by your single select fields by specifying the option, for example: fieldname:option. You can filter for multiple values by providing a comma-separated list of options, for example: fieldname:option,option. For more information, see AUTOTITLE.
Single select fields can contain up to 50 options.
Adding a ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md",
"title": "About single select fields"
} |
You can use text fields to include notes or any other freeform text in your project.
Text fields can be used in filters, for example: field:"exact text". Text fields and item titles will also be used if you filter for text without specifying a field.
Number fields can also be used in filters. You can use , =, <, <=, an... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md",
"title": "About text and number fields"
} |
If your organization uses issue types, you can enable the "Type" field on your projects to see the issue type and how the issue is classified in your organization, such as a bug, task, or feature.
For more about issue types, see AUTOTITLE.
Enabling the Type field
You can enable the "Type" field to see the type of the ... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/about-the-issue-type-field.md",
"title": "About the issue type field"
} |
1. Click the name of the custom field you want to delete.
1. Click Delete field.
!Screenshot showing the settings for a note field. The "Delete field" button is highlighted with an orange outline. | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/deleting-custom-fields.md",
"title": "Deleting custom fields"
} |
1. Click the name of the custom field you want to rename.
1. Under "Field name", type the new name for the field.
1. To save changes, press <kbdReturn</kbd. | {
"source": "github-docs/issues/planning-and-tracking-with-projects/understanding-fields/renaming-custom-fields.md",
"title": "Renaming custom fields"
} |
You can use insights for to view, create, and customize charts that use the items added to your project as their source data. You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to an... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md",
"title": "About insights for {% data variables.product.prodname_projects_v2 %}"
} |
1. In the menu on the left, click on the chart you would like to configure.
1. On the right side of the page, click Configure. A panel will open on the right.
1. To change the type of chart, select the Layout dropdown and click on the chart type you want to use.
1. To change the field used for your chart's X-axis, sele... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md",
"title": "Configuring charts"
} |
1. In the menu on the left, click New chart.
1. Optionally, to change the name of the new chart, click , type a new name, and press <kbdReturn</kbd.
1. Above the chart, type filters to change the data used to build the chart. For more information, see AUTOTITLE.
1. To the right of the filter text box, click Save change... | {
"source": "github-docs/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md",
"title": "Creating charts"
} |
To clone an open issue, you must have triage access to the repository that contains the original issue and to the destination repository. The destination repository must allow blank issues. See AUTOTITLE.
When you clone an issue, a new issue is created with the original issue's title, description, assignees, type, labe... | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/cloning-an-issue.md",
"title": "Cloning an issue"
} |
[!NOTE]
You can also close issues automatically with keywords in pull requests and commit messages. For more information, see AUTOTITLE.
1. In the list of issues, click the issue you'd like to close.
1. Optionally, to change your reason for closing the issue, next to "Close issue," select , then click a reason.
!Sc... | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue.md",
"title": "Closing an issue"
} |
The ability to delete issues depends on whether the repository is owned by a personal account or an organization:
The only account that can delete issues in a repository owned by a personal account is that account.
Only accounts with admin or owner permissions can delete issues in a repository owned by an organizatio... | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue.md",
"title": "Deleting an issue"
} |
For a "marked as duplicate" timeline event to appear, the user who creates the duplicate reference comment must have write access to the repository where they create the comment.
Marking duplicates
To mark an issue or pull request as a duplicate, type "Duplicate of" followed by an issue or pull request number in the b... | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/marking-issues-or-pull-requests-as-a-duplicate.md",
"title": "Marking issues or pull requests as a duplicate"
} |
1. In the list of issues, click the issue you'd like to pin.
1. In the right sidebar, click Pin issue. | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/pinning-an-issue-to-your-repository.md",
"title": "Pinning an issue to your repository"
} |
To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see AUTOTITLE.
[!NOTE]
You can only transfer issues between repositories owned by the same user or organization account. A private re... | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository.md",
"title": "Transferring an issue to another repository"
} |
About the AI-powered issue intake tool
The AI-powered issue intake tool helps you automate the triage process for new issues in your repository. Open source maintainers and project managers are often inundated with new issues, many of which may lack necessary information, or are not actionable. This tool leverages AI t... | {
"source": "github-docs/issues/tracking-your-work-with-issues/administering-issues/triaging-an-issue-with-ai.md",
"title": "Triaging an issue with AI"
} |
You can create issues in your repository to plan, discuss, and track work. Issues are quick to create, flexible, and can be used in many ways. Issues can track bug reports, new features and ideas, and anything else you need to write down or discuss with your team, and you can use to plan and track the work for your te... | {
"source": "github-docs/issues/tracking-your-work-with-issues/learning-about-issues/about-issues.md",
"title": "About issues"
} |
Introduction
You can use 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 i... | {
"source": "github-docs/issues/tracking-your-work-with-issues/learning-about-issues/planning-and-tracking-work-for-your-team-or-project.md",
"title": "Planning and tracking work for your team or project"
} |
Introduction
This guide demonstrates how to use to plan and track a piece of work. In this guide, you will create a new issue and break it down into sub-issues. You'll also learn how to add labels, issue types, milestones, assignees, and projects to communicate metadata about your issue.
Prerequisites
To create an is... | {
"source": "github-docs/issues/tracking-your-work-with-issues/learning-about-issues/quickstart.md",
"title": "Quickstart for GitHub Issues"
} |
[!NOTE]
Slash commands are currently in and subject to change.
About slash commands
Slash commands make it easier to type more complex Markdown, such as tables, tasklists, and code blocks.
You can use slash commands in any description or comment field in issues, pull requests, or discussions where that slash command... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/about-slash-commands.md",
"title": "About slash commands"
} |
Issue fields appear in the right-hand sidebar of issues, alongside system fields like assignees, labels, and type. You can set values when creating or editing an issue. When you select an issue type while creating an issue, any fields pinned to that type automatically appear in the sidebar.
[!NOTE]
Issue fields are c... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/adding-and-managing-issue-fields.md",
"title": "Adding and managing issue fields"
} |
You can add sub-issues to an issue to break down larger pieces of work into tasks. Your sub-issues show their relationship to the parent issue allowing you to track your work across . Parent issues and sub-issue progress is also available in your , allowing you to build views, filter, and group by parent issue.
Your su... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues.md",
"title": "Adding sub-issues"
} |
About issue and pull request assignees
You can assign multiple people to each issue or pull request, including: yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. For more information, see AU... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users.md",
"title": "Assigning issues and pull requests to other GitHub users"
} |
Navigating issue hierarchy
You can browse through all levels of sub-issues from the parent issue.
1. Navigate to the parent issue.
1. To view the sub-issues under another sub-issue, click the expand toggle ().
!Screenshot of a sub-issues section. The expand toggle is highlighted with an orange rectangle.
Finding a ... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues.md",
"title": "Browsing sub-issues"
} |
[!NOTE]
The ability to create a branch for an issue is currently in and subject to change.
About branches connected to an issue
Branches connected to an issue are shown under the "Development" section in the sidebar of an issue. When you create a pull request for one of these branches, it is automatically linked to ... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/creating-a-branch-for-an-issue.md",
"title": "Creating a branch to work on an issue"
} |
Issues can be used to keep track of bugs, enhancements, or other requests. For more information, see AUTOTITLE.
Creating an issue from a repository
1. If your repository uses issue templates, next to the type of issue you'd like to open, click Get started.
If the type of issue you'd like to open isn't included in t... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md",
"title": "Creating an issue"
} |
Query parameter Example
--- ---
title https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report creates an issue with the label "bug" and title "New bug report."
body https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem. creates an issue with the ti... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/creating-an-issue.md",
"title": "Creating an issue"
} |
Issue dependencies let you define issues that are blocked by, or blocking, other work.
Marking an issue as blocked by, or blocking, another issue
1. Navigate to the issue that you want to create a dependency for.
1. In the right sidebar, click Relationships.
1. From the dropdown, select a dependency option:
To ind... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/creating-issue-dependencies.md",
"title": "Creating issue dependencies"
} |
Editing an issue title
You can edit an issue's title. The change to the title is added to the issue's timeline.
1. Navigate to the issue you want to edit.
1. To the right of the issue title, click Edit.
!Screenshot of an issue header, the "Edit" button is highlighted with an orange outline.
1. Type your new title.
1... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md",
"title": "Editing an issue"
} |
Filtering issues and pull requests
Issues and pull requests come with a set of default filters you can apply to organize your listings.
You can filter issues and pull requests to find:
All open issues and pull requests
Issues and pull requests that you've created
Issues and pull requests that are assigned to you
Is... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md",
"title": "Filtering and searching issues and pull requests"
} |
About linked issues and pull requests
You can link an issue to a pull request manually or using a supported keyword in the pull request description, that is, the summary text added by the author when they created the pull request.
When you link a pull request to the issue the pull request addresses, collaborators can s... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md",
"title": "Linking a pull request to an issue"
} |
Linked issue Syntax Example
--------------- ------ ------
Issue in the same repository KEYWORD ISSUE-NUMBER Closes 10
Issue in a different repository KEYWORD OWNER/REPOSITORYISSUE-NUMBER Fixes octo-org/octo-repo100
Multiple issues Use full syntax for each issue Resolves 10, resolves 123, resolves octo-org/oct... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md",
"title": "Linking a pull request to an issue"
} |
Issue fields let you add structured metadata to issues across your organization. Instead of relying on labels or free-text workarounds, you can create fields like priority, effort, impact, or any custom category your team needs. Fields are defined at the organization level and apply across all repositories in your orga... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/managing-issue-fields-in-your-organization.md",
"title": "Managing issue fields in your organization"
} |
You can use issue types to classify and manage different types of issues across your organization. You can create up to issue types that your organization members can apply to issues, making it easier for you and your members to find issues and plan work.
Default issue types are included in every organization, but the... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization.md",
"title": "Managing issue types in an organization"
} |
Viewing your issues and pull requests
Your issue and pull request dashboards are available at the top of any page. On each dashboard, you can filter the list to find issues or pull requests you created, that are assigned to you, or in which you're mentioned. You can also find pull requests that you've been asked to rev... | {
"source": "github-docs/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md",
"title": "Viewing all issues and pull requests"
} |
When you create a milestone, you can associate it with issues and pull requests.
To better manage your project, you can view details about your milestone. From the milestone page, you can see:
A user-provided description of the milestone, which can include information like a project overview, relevant teams, and proje... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/about-milestones.md",
"title": "About milestones"
} |
1. Select the checkbox next to the items you want associated with a milestone.
!Screenshot of the first two items in a list of issues. To the left of each issue, a checkbox is checked and outlined in dark orange.
1. Above the list of issues or pull requests, select the Milestone dropdown menu.
!Screenshot of the ... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests.md",
"title": "Associating milestones with issues and pull requests"
} |
1. Choose one of these options:
To create a new milestone, click New Milestone.
To edit a milestone, next to the milestone you want to edit, click Edit.
!Screenshot of the list of milestones. Within the entry for the "beta release" milestone, a link, labeled "Edit," is outlined in dark orange. <!-- mar... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md",
"title": "Creating and editing milestones for issues and pull requests"
} |
[!TIP]
If you'd rather filter issues and pull requests using the Search bar, you can use the milestone search syntax. For a milestone called My Milestone, the search syntax would be: milestone:"My Milestone".
To clear your filter selection, click Clear current search query, filters, and sorts.
You can also filter... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md",
"title": "Filtering issues and pull requests by milestone"
} |
About labels
You can manage your work on by creating labels to categorize issues, pull requests, and discussionsissues and pull requests. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any issue, pull request, or discussionissue or pull request within tha... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/managing-labels.md",
"title": "Managing labels"
} |
Label Description
--- ---
bug Indicates an unexpected problem or unintended behavior
documentation Indicates a need for improvements or additions to documentation
duplicate Indicates similar issues, pull requests, or discussionsissues or pull requests
enhancement Indicates new feature requests
good first issue ... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/managing-labels.md",
"title": "Managing labels"
} |
1. In the upper-right corner, click Milestones.
!Screenshot of the list of issues for a repository. Above the list, a button, labeled with a signpost icon and "Milestones," is outlined in orange.
1. Click the milestone you wish to see more information about.
To better manage your project, you can prioritize issues o... | {
"source": "github-docs/issues/using-labels-and-milestones-to-track-work/viewing-your-milestones-progress.md",
"title": "Viewing your milestone's progress"
} |
Configure Azure Pipelines and Azure Boards
If you used Azure Pipelines or Azure Boards previously and want to continue using them with your repositories now they are hosted on , you can follow these guides on Microsoft Learn to configure the relevant extension.
Connect Azure Pipelines to GitHub
Configure the Azure Bo... | {
"source": "github-docs/migrations/ado/follow-up-tasks.md",
"title": "Follow-up tasks"
} |
To allow someone other than an organization owner to run a migration or download migration logs, you can grant the migrator role to a user or team.
To grant the migrator role using the CLI, you can use the .
1. On , create and record a that has the admin:org scope.
1. Use the gh ado2gh grant-migrator-role command, rep... | {
"source": "github-docs/migrations/ado/granting-the-migrator-role.md",
"title": "Granting the migrator role"
} |
Step 1: Install the
GitHub Enterprise Importer is a collection of extensions for . If this is your first migration, you'll need to install and the .
Step 2: Set environment variables
Before you can use the to migrate to , you must create s that can access the source and destination organizations, then set the s as ... | {
"source": "github-docs/migrations/ado/install-and-configure-github-enterprise-importer.md",
"title": "Install and configure GitHub Enterprise Importer"
} |
If you're a member of an organization that has migrated from Azure DevOps to , this guide will explain the changes in your workflows to make the migration as smooth as possible.
Structure
In Azure DevOps, repositories are nested inside team projects, so the structure of your environment looks like this:
Organization
... | {
"source": "github-docs/migrations/ado/key-differences-between-azure-devops-and-github.md",
"title": "Key differences between Azure DevOps and GitHub"
} |
To migrate repositories from Azure DevOps to , you need sufficient access to the source (an organization on Azure DevOps) and the destination (an organization on ). After you complete the steps in this article, your access and permissions will ready for your migration.
Decide who will perform the migration
If the pers... | {
"source": "github-docs/migrations/ado/manage-access.md",
"title": "Manage access"
} |
Prerequisites
You must have completed all previous phases of this guide.
For more information, see AUTOTITLE.
Generate a migration script
To generate a migration script, run the gh ado2gh generate-script command.
gh ado2gh generate-script --ado-org SOURCE --github-org DESTINATION --output FILENAME
Additional argum... | {
"source": "github-docs/migrations/ado/migrate-your-repositories-from-azure-devops-to-github.md",
"title": "Migrate your repositories from Azure DevOps to GitHub"
} |
Determine how much you have to migrate
Determine your timeline, which will largely dictate your approach. The first step for determining your timeline is to get an inventory of what you need to migrate.
Number of repositories
Number of pull requests
[!NOTE] Migration timing is largely based on the number of pull requ... | {
"source": "github-docs/migrations/ado/prepare-for-your-migration-from-azure-devops-to-github.md",
"title": "Prepare for your migration from Azure DevOps to GitHub"
} |
Team Access to migrated repositories
--- ---
TEAM-PROJECT-Maintainers Maintainer
TEAM-PROJECT-Admins Admin
To give access to migrated repositories, you can add people to these teams. You can do this manually on , or if you chose to link the teams to Azure Active Directory (AAD) groups during your migration, by mana... | {
"source": "github-docs/migrations/ado/prepare-for-your-migration-from-azure-devops-to-github.md",
"title": "Prepare for your migration from Azure DevOps to GitHub"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.