jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-10 09:02:35 -05:00
Code Issues Projects Releases Wiki Activity

Merge branch 'main' into openapi-update-7c7d0771b0560f90e5e70d48f0b6e8059ebf0f470a269adad8c3b034a7c1c702

Browse Source
This commit is contained in:
Sarita Iyer
2022-01-13 15:53:37 -05:00
committed by GitHub
parent 7ad696400b 275c3c2a53
commit 4d644ea462
2 changed files with 28 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
View File

@@ -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)"

28
data/reusables/actions/actions-group-concurrency.md
View File

@@ -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 %}