From 8ba1aeca173afe19c082d5bae964f0e578226917 Mon Sep 17 00:00:00 2001 From: Chris Buckley Date: Mon, 10 Jan 2022 02:38:38 +0000 Subject: [PATCH 1/3] Remove circular link The article linked back to itself as further reading. --- .../viewing-contributions-on-your-profile.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 390e4d81e0..78f74ca3f7 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -98,7 +98,3 @@ The contribution activity section includes a detailed timeline of your work, inc If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." {% endif %} - -## Further reading - -- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" From 7ae281cc49f45e9da2e60d9d3e67a65ab045dab2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Machist=C3=A9=20N=2E=20Quintana?= Date: Thu, 13 Jan 2022 14:39:48 -0500 Subject: [PATCH 2/3] Update docs on using concurrency to auto-cancel redundant jobs / runs (#11244) Co-authored-by: Sarah Edwards --- .../actions/actions-group-concurrency.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/data/reusables/actions/actions-group-concurrency.md b/data/reusables/actions/actions-group-concurrency.md index c973058ca4..7a666d419f 100644 --- a/data/reusables/actions/actions-group-concurrency.md +++ b/data/reusables/actions/actions-group-concurrency.md @@ -23,3 +23,31 @@ concurrency: cancel-in-progress: true ``` {% endraw %} + +### Example: Using a fallback value + +If you build the group name with a property that is only defined for specific events, you can use a fallback value. For example, `github.head_ref` is only defined on `pull_request` events. If your workflow responds to other events in addition to `pull_request` events, you will need to provide a fallback to avoid a syntax error. The following concurrency group cancels in-progress jobs or runs on `pull_request` events only; if `github.head_ref` is undefined, the concurrency group will fallback to the run ID, which is guaranteed to be both unique and defined for the run. + +{% raw %} +```yaml +concurrency: + group: ${{ github.head_ref || github.run_id }} + cancel-in-progress: true +``` +{% endraw %} + + +### Example: Only cancel in-progress jobs or runs for the current workflow + + If you have multiple workflows in the same repository, concurrency group names must be unique across workflows to avoid canceling in-progress jobs or runs from other workflows. Otherwise, any previously in-progress or pending job will be canceled, regardless of the workflow. + +To only cancel in-progress runs of the same workflow, you can use the `github.workflow` property to build the concurrency group: + +{% raw %} +```yaml +concurrency: + group: ${{ github.workflow }}-${{ github.ref }} + cancel-in-progress: true +``` +{% endraw %} + From 763e1949a7ec8bcc3c0a10715cfcd1f77df75112 Mon Sep 17 00:00:00 2001 From: mc <42146119+mchammer01@users.noreply.github.com> Date: Thu, 13 Jan 2022 19:41:20 +0000 Subject: [PATCH 3/3] Secret scanning as a push protection (#24202) * add publicly available reusable to docs-internal * add related publicly available screenshot * Empty commit * Empty commit * Empty commit * Empty commit * Remove staff-shipped change * Empty commit * Empty commit * Empty commit Co-authored-by: Felicity Chapman Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>