Merge pull request #19223 from github/repo-sync

repo sync

content/actions/guides/caching-dependencies-to-speed-up-workflows.md

@@ -59,7 +59,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
 
 - `key`: **Required** The key created when saving a cache and the key used to search for a cache. Can be any combination of variables, context values, static strings, and functions. Keys have a maximum length of 512 characters, and keys longer than the maximum length will cause the action to fail.
 - `path`: **Required** The file path on the runner to cache or restore. The path can be an absolute path or relative to the working directory.
-  - With `v2` of the `cache` action, you can specify a single path, or multiple paths as a list. Paths can be either directories or single files, and glob patterns are supported.
+  - Paths can be either directories or single files, and glob patterns are supported.
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. For example:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - With `v1` of the `cache` action, only a single path is supported and it must be a directory. You cannot cache a single file.
 - `restore-keys`: **Optional** An ordered list of alternative keys to use for finding the cache if no cache hit occurred for `key`.
 

content/codespaces/about-codespaces.md

@@ -28,7 +28,6 @@ A codespace includes everything developers need to develop for a specific reposi
 
 Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
 
-
 ### A consistent environment
 
 You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."

content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md

@@ -0,0 +1,25 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+  !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**.
+  !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)

content/sponsors/receiving-sponsorships-through-github-sponsors/index.md

@@ -20,3 +20,5 @@ versions:
 {% link_with_intro /managing-your-payouts-from-github-sponsors %}
 {% link_with_intro /contacting-your-sponsors %}
 {% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}

content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md

@@ -0,0 +1,23 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**.
+  !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account".
+  !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)