@@ -133,6 +133,20 @@ Email notifications from {% data variables.product.prodname_dotcom %} contain he
|
||||
| `List-Id` field | This field identifies the name of the repository and its owner. The format of this address is always `OWNER/REPOSITORY <REPOSITORY.OWNER>`, e.g. `List-Id: grain-lang/grain <grain.grain-lang.{% data variables.product.product_url %}>`. |
|
||||
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." |
|
||||
|
||||
## Replying to email notifications
|
||||
|
||||
You can reply to email notifications from {% data variables.product.product_name %} and your reply will be posted to the issue, pull request, or discussion.
|
||||
|
||||
The `reply-to` address on each email notification identifies the thread and the account that the comment will be posted from. This email address remains valid until you reset your password.
|
||||
|
||||
{% data variables.product.product_name %} will not always include the full email contents and will attempt to strip some personally identifiable information from comments created via an email reply:
|
||||
|
||||
* Email addresses in a standard format, such as `octocat@github.com`, are transformed to `***@***.***`.
|
||||
* Signatures and quoted reply chains, when the email client has used a `>` to mark those sections, are stripped.
|
||||
* While the unsubscribe link from your email notification is sometimes quoted, the link will only work when signed in to your account.
|
||||
* Email attachments are not included in the resulting comment.
|
||||
* The maximum length of a comment created via an email reply is 65530 characters.
|
||||
|
||||
## Choosing your notification settings
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: 'Exporting your {% data variables.projects.project_v2 %} data'
|
||||
shortTitle: 'Exporting your {% data variables.projects.project_v2 %} data'
|
||||
intro: 'Learn about exporting your {% data variables.projects.project_v2 %} data.'
|
||||
permissions: 'People who can access a project can export a view. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."'
|
||||
versions:
|
||||
feature: projects-v2
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
You can download a view as a _.tsv_ (tab-separated) file.
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
|
||||
1. Click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||

|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
|
||||
1. Click {% ifversion ghes < 3.11 %}**Download**{% else %}**Export view data**{% endif %}.
|
||||
@@ -13,5 +13,6 @@ children:
|
||||
- /closing-and-deleting-your-projects
|
||||
- /adding-your-project-to-a-repository
|
||||
- /adding-your-project-to-a-team
|
||||
- /exporting-your-projects-data
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
@@ -132,7 +132,7 @@ mutation startRepositoryMigration (
|
||||
```
|
||||
|
||||
{% data reusables.enterprise-migration-tool.startRepositoryMigration-table-ec %}
|
||||
| `sourceRepositoryUrl` | The URL of your source repository, using the format `https://dev.azure.com/{organization}/_git/{repository}`.
|
||||
| `sourceRepositoryUrl` | The URL of your source repository, using the format `https://dev.azure.com/{organization}/{project}/_git/{repository}`.
|
||||
|
||||
For {% data variables.product.pat_generic %} requirements, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/managing-access-for-a-migration-from-azure-devops#required-scopes-for-personal-access-tokens)."
|
||||
|
||||
|
||||
Reference in New Issue
Block a user