Skip to content

Commit 0f8e10a

Browse files
authored
Branch was updated using the 'autoupdate branch' Actions workflow.
2 parents e81255c + 8359a28 commit 0f8e10a

2 files changed

Lines changed: 2 additions & 3 deletions

File tree

content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,5 @@ Once you have {% if enterpriseServerVersions contains currentVersion or currentV
3636
{% if currentVersion == "free-pro-team@latest" %}
3737
### Third-party backup tools
3838

39-
A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
40-
41-
You can back up all of a repository's Git data (such as project files and commit history), as well as much data from {% data variables.product.product_name %} (such as issues and pull requests), with [BackHub](https://github.com/marketplace/backhub), which creates daily recurring backups of your repositories with snapshots up to 30 days back in time. BackHub is available in {% data variables.product.prodname_marketplace %}.
39+
A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." For more information about self-service backup tools, see the [Backup Utilities category on {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities).
4240
{% endif %}

content/github/site-policy/github-subprocessors-and-cookies.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@ Since the number and names of cookies may change, the table below may be updated
5050
| Service Provider | Cookie Name | Description | Expiration* |
5151
|:---|:---|:---|:---|
5252
| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
53+
| GitHub | `color_mode` | This cookie is used to indicate the user selected theme preference. | session |
5354
| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year |
5455
| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year |
5556
| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks |

0 commit comments

Comments
 (0)