content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
script defined in `ACTIONS\_RUNNER\_HOOK\_JOB\_COMPLETED` is executed at the end of the job, before the job completes. This makes it unsuitable for use cases that may interrupt a runner, such as deleting the runner machine as part of an autoscaling implementation. ## Troubleshooting ### Permission denied If you get a "... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/run-scripts.md | main | github-actions | [
-0.006787208840250969,
0.02358417771756649,
-0.06520617753267288,
0.015459259040653706,
0.046417318284511566,
-0.025413038209080696,
-0.08957750350236893,
0.03151104226708412,
0.011994564905762672,
0.002656008582562208,
-0.0008622584864497185,
0.032591015100479126,
-0.047076769173145294,
-... | 0.085986 |
{% data reusables.actions.enterprise-github-hosted-runners %} For information on how to use labels to route jobs to specific types of self-hosted runners, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow). You can also route jobs to runners in a spec... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/apply-labels.md | main | github-actions | [
-0.01636902056634426,
-0.012904131785035133,
-0.10707495361566544,
0.06971278786659241,
-0.0003988993994425982,
0.034358058124780655,
0.0016728945774957538,
-0.0021736028138548136,
-0.05833357200026512,
-0.013691888190805912,
-0.01678863912820816,
-0.032332759350538254,
-0.006597763858735561... | 0.162095 |
an existing self-hosted runner. For example, this command assigns a label named `gpu` when configuring a new self-hosted runner: ```shell ./config.sh --url --token --labels gpu ``` The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/apply-labels.md | main | github-actions | [
0.035688113421201706,
-0.004292472265660763,
-0.123772032558918,
-0.004241139627993107,
0.003006769111379981,
0.051412202417850494,
-0.005907493177801371,
0.07768867909908295,
-0.03360501676797867,
-0.059480324387550354,
0.025311818346381187,
-0.06302659958600998,
0.012541048228740692,
-0.... | 0.108439 |
{% data reusables.actions.enterprise-github-hosted-runners %} {% ifversion repository-actions-runners %} ## Viewing available runners for a repository {% data reusables.actions.about-viewing-runner-list %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/use-in-a-workflow.md | main | github-actions | [
-0.007401264738291502,
-0.06525859236717224,
-0.09297807514667511,
0.10036316514015198,
0.03969189152121544,
0.026895688846707344,
-0.01342795416712761,
0.02508397400379181,
-0.02743634209036827,
0.0363512746989727,
0.05281902104616165,
0.007345760241150856,
0.012484695762395859,
-0.017780... | 0.095243 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Creating a self-hosted runner group for an organization {% data reusables.actions.self-hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-organization %} {% ifversion ghec or ghes %} ## Creating a self-hosted run... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/manage-access.md | main | github-actions | [
0.009563063271343708,
0.01004393957555294,
-0.07793564349412918,
0.07146517932415009,
0.02153150364756584,
-0.014411554671823978,
-0.030155695974826813,
-0.04718857258558273,
-0.059083208441734314,
0.03397565335035324,
0.037878528237342834,
-0.014755458571016788,
0.01029940415173769,
-0.01... | 0.077458 |
> [!WARNING] > {% data reusables.actions.self-hosted-runner-security %} > > For more information, see [AUTOTITLE](/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions). {% data reusables.actions.enterprise-github-hosted-runners %} ## Prerequisites Before you add a self-hosted runne... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/add-runners.md | main | github-actions | [
0.002924761502072215,
-0.004959973972290754,
-0.07652894407510757,
0.0765024796128273,
0.025187747552990913,
-0.00259195314720273,
-0.033068396151065826,
0.04511794447898865,
-0.057317741215229034,
0.03808555006980896,
0.00775507465004921,
-0.03328203409910202,
0.037974074482917786,
0.0182... | 0.098119 |
organization. For more information on changing runner group access settings, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group). {% endif %} ## Next steps You can set up automation t... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/add-runners.md | main | github-actions | [
0.03417457640171051,
0.008506094105541706,
-0.0465472936630249,
0.06491197645664215,
-0.035596948117017746,
-0.005934168118983507,
-0.08694427460432053,
0.009987955912947655,
-0.020038487389683723,
0.023523101583123207,
-0.05280088260769844,
-0.0006460912991315126,
-0.02446269989013672,
0.... | 0.102391 |
{% data reusables.actions.enterprise-github-hosted-runners %} {% capture service\_first\_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %} {% capture service\_non\_windows\_intro\_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/configure-the-application.md | main | github-actions | [
0.02885517105460167,
-0.045037563890218735,
-0.045187368988990784,
0.022694194689393044,
0.004068492911756039,
-0.0061440421268343925,
-0.051145922392606735,
0.06947360932826996,
-0.0291802566498518,
0.042808692902326584,
-0.012545903213322163,
-0.005193445831537247,
0.009862479753792286,
... | 0.096383 |
the following command: {% linux %} ```shell sudo ./svc.sh uninstall ``` {% endlinux %} {% windows %} ```shell Remove-Service "{{ service\_win\_name }}" ``` {% endwindows %} {% mac %} ```shell ./svc.sh uninstall ``` {% endmac %} {% linux %} ## Customizing the self-hosted runner service If you don't want to use the above... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/configure-the-application.md | main | github-actions | [
-0.013776851817965508,
0.02528238855302334,
-0.04390836879611015,
-0.003837005700916052,
0.02094476856291294,
-0.004610559903085232,
-0.06300026178359985,
0.03572969511151314,
0.023607555776834488,
0.0590125173330307,
-0.03942091017961502,
0.04688587039709091,
-0.08472907543182373,
0.02823... | 0.110644 |
> [!NOTE] > This feature is currently in {% data variables.release-phases.public\_preview %} and is subject to change. {% data reusables.actions.enterprise-github-hosted-runners %} ## About container customization {% data variables.product.prodname\_actions %} allows you to run a job within a container, using the `cont... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/customize-containers.md | main | github-actions | [
0.011612956412136555,
-0.002485426841303706,
-0.04881567507982254,
0.047288186848163605,
0.009448649361729622,
-0.00891561433672905,
-0.017840128391981125,
0.02619667537510395,
-0.04784119129180908,
0.023878946900367737,
-0.05378860980272293,
0.004348545800894499,
-0.00944633036851883,
-0.... | 0.131522 |
the Docker container. \* `targetVolumePath`: \*\*Required\*\*. The target path to the volume that will be mounted into the Docker container. \* `readOnly`: \*\*Required\*\*. Determines whether or not the mount should be read-only. \* `systemMountVolumes`: \*\*Required\*\*. An array of mounts to mount into the container... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/customize-containers.md | main | github-actions | [
0.04706435650587082,
0.008787380531430244,
-0.02676478773355484,
-0.005948062986135483,
-0.02359357289969921,
-0.012720845639705658,
-0.005832947790622711,
0.013257259503006935,
0.011838020756840706,
0.009389483369886875,
-0.061775390058755875,
-0.09866867959499359,
0.030411772429943085,
-... | -0.028621 |
following tasks in the `cleanup\_job` command: \* Stop any running service or job containers (or the equivalent pod). \* Stop the network (if one exists). \* Delete any job or service containers (or the equivalent pod). \* Delete the network (if one exists). \* Cleanup anything else that was created for the job. #### A... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/customize-containers.md | main | github-actions | [
-0.06463707238435745,
0.03857402130961418,
0.005261649843305349,
-0.004018450155854225,
0.015185930766165257,
-0.09254618734121323,
0.012462501414120197,
-0.09110505878925323,
0.018768267706036568,
0.04493945091962814,
0.020816681906580925,
0.019847000017762184,
-0.031383026391267776,
0.01... | 0.160603 |
"/home/octocat/git/runner/\_layout/\_work", "targetVolumePath": "/\_\_w", "readOnly": false }, { "sourceVolumePath": "/home/octocat/git/runner/\_layout/externals", "targetVolumePath": "/\_\_e", "readOnly": true }, { "sourceVolumePath": "/home/octocat/git/runner/\_layout/\_work/\_temp", "targetVolumePath": "/\_\_w/\_tem... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/customize-containers.md | main | github-actions | [
-0.029407331719994545,
-0.0333772674202919,
-0.03832487389445305,
0.06705189496278763,
0.023632487282156944,
-0.05493566021323204,
0.006507680751383305,
0.0385824590921402,
0.05914446711540222,
-0.023118266835808754,
0.027862662449479103,
-0.030165042728185654,
0.0117788165807724,
-0.01379... | 0.103251 |
variable, as described in the next section. ## Triggering the customization script The custom script must be located on the runner, but should not be stored in the self-hosted runner application directory (that is, the directory into which you downloaded and unpacked the runner software). The scripts are executed in th... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/customize-containers.md | main | github-actions | [
0.0158848874270916,
0.02640349604189396,
-0.03145504370331764,
0.041010499000549316,
0.024136994034051895,
-0.01364055834710598,
-0.013844138942658901,
0.013274425640702248,
-0.03887983784079552,
0.03183189034461975,
-0.05398028343915939,
-0.004950753413140774,
-0.023917565122246742,
-0.03... | 0.09996 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Removing a runner from a repository > [!NOTE] > \* {% data reusables.actions.self-hosted-runner-removal-impact %} > \* {% data reusables.actions.self-hosted-runner-auto-removal %} > \* {% data reusables.actions.jit-runner-removal %} To remove a self-hoste... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/self-hosted-runners/remove-runners.md | main | github-actions | [
-0.02310332842171192,
0.0498824417591095,
-0.020081521943211555,
0.054806943982839584,
0.02413451112806797,
-0.029620392248034477,
0.0015806038863956928,
-0.061734434217214584,
-0.010155493393540382,
0.012631298042833805,
0.043955665081739426,
0.03903577849268913,
0.02467607893049717,
0.00... | 0.102197 |
{% data reusables.actions.enterprise-github-hosted-runners %} If you require additional software packages on {% data variables.product.prodname\_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow. To see which packages are already installed by default, see [AUTOTITLE](/ac... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/github-hosted-runners/customize-runners.md | main | github-actions | [
-0.05239120498299599,
-0.09391630440950394,
-0.030186010524630547,
-0.003522201906889677,
0.004114874172955751,
0.017780302092432976,
-0.01170984748750925,
0.018682893365621567,
-0.05044054985046387,
-0.016839291900396347,
0.01585165038704872,
0.04225406423211098,
-0.007451449986547232,
-0... | 0.094747 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Viewing active jobs in your organization or enterprise You can get a list of all jobs currently running on {% data variables.product.prodname\_dotcom %}-hosted runners in your organization or enterprise. {% data reusables.actions.github-hosted-runners-nav... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/github-hosted-runners/view-current-jobs.md | main | github-actions | [
-0.03251437470316887,
-0.12564215064048767,
-0.10509536415338516,
0.062276411801576614,
0.039495326578617096,
-0.025693995878100395,
0.011733009479939938,
-0.03958805650472641,
-0.06855882704257965,
0.03850358724594116,
0.010799377225339413,
0.0801134705543518,
0.01319141499698162,
-0.0636... | 0.16322 |
{% ifversion ghes %} {% data reusables.actions.enterprise-github-hosted-runners %} {% else %} ## Using a {% data variables.product.prodname\_dotcom %}-hosted runner To use a {% data variables.product.prodname\_dotcom %}-hosted runner, create a job and use `runs-on` to specify the type of runner that will process the jo... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/github-hosted-runners/use-github-hosted-runners.md | main | github-actions | [
-0.011719970963895321,
-0.050182044506073,
-0.07549808919429779,
0.03061189502477646,
0.05015356093645096,
0.002302001230418682,
-0.020812563598155975,
0.04552649334073067,
-0.06488040834665298,
0.0026718084700405598,
-0.011422115378081799,
0.01854548044502735,
-0.01978553831577301,
-0.024... | 0.133876 |
## Using WireGuard to create a network overlay {% data reusables.actions.private-networking-wireguard-intro %} There are various disadvantages to this approach: \* To reach WireGuard running on your private service, you will need a well-known IP address and port that your workflow can reference: this can either be a pu... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/github-hosted-runners/connect-to-a-private-network/connect-with-wireguard.md | main | github-actions | [
-0.13493239879608154,
0.024708179756999016,
-0.06339115649461746,
0.003090024460107088,
-0.027093909680843353,
0.015278236009180546,
0.06529318541288376,
0.07459461688995361,
-0.10598132759332657,
-0.01072700135409832,
0.006622400134801865,
0.02420603111386299,
0.027838990092277527,
-0.054... | 0.10078 |
## Using an API gateway with OIDC {% data reusables.actions.private-networking-oidc-intro %} For example, you could run an API gateway on the edge of your private network that authenticates incoming requests with the OIDC token and then makes API requests on behalf of your workflow in your private network. The followin... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-runners/github-hosted-runners/connect-to-a-private-network/connect-with-oidc.md | main | github-actions | [
-0.09762077033519745,
0.010317385196685791,
-0.06386829912662506,
0.018963899463415146,
-0.003781393636018038,
-0.012349122203886509,
0.05971617251634598,
0.0712621882557869,
0.016216006129980087,
-0.053839899599552155,
-0.02697952836751938,
0.03724271059036255,
0.008112427778542042,
-0.01... | 0.047802 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Creating workflow templates This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the workflow templates will be presented to users when they are creating a new workflow. 1. If it doesn't already ... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/create-workflow-templates.md | main | github-actions | [
0.018826307728886604,
-0.04038485512137413,
-0.0564633272588253,
0.019162843003869057,
-0.03266856074333191,
0.007908359169960022,
-0.05124394968152046,
0.028193984180688858,
0.04626315087080002,
0.036886170506477356,
-0.06479363888502121,
-0.0023293436970561743,
-0.03447530046105385,
-0.0... | 0.068179 |
> [!WARNING] > \* {% data reusables.actions.outside-collaborators-actions %} > \* {% data reusables.actions.scoped-token-note %} ## Sharing actions and workflows from your private repository 1. Store the action or reusable workflow in a private repository. For more information, see [AUTOTITLE](/repositories/creating-an... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/share-across-private-repositories.md | main | github-actions | [
-0.08320038765668869,
-0.04021430388092995,
-0.062207501381635666,
0.034884270280599594,
0.015317081473767757,
0.07662631571292877,
0.1073792427778244,
-0.0015190041158348322,
-0.04468369111418724,
0.017732836306095123,
0.05669165775179863,
-0.017931798473000526,
0.023859230801463127,
-0.0... | 0.086568 |
## Overview If your organization is owned by an enterprise account, you can share actions and reusable workflows within your enterprise, without publishing them publicly, by allowing {% data variables.product.prodname\_actions %} workflows to access an internal or private repository that contains the action or reusable... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/share-with-your-enterprise.md | main | github-actions | [
-0.0653415396809578,
-0.0714145079255104,
-0.10385026782751083,
0.0005955437663942575,
0.016959629952907562,
0.05863440781831741,
0.06972675770521164,
-0.007645894773304462,
0.018844353035092354,
-0.0017958430107682943,
0.023173045367002487,
0.04098976403474808,
0.011082387529313564,
-0.00... | 0.158519 |
> [!WARNING] > \* {% data reusables.actions.outside-collaborators-actions %} > \* {% data reusables.actions.scoped-token-note %} ## Sharing actions and workflows with your organization 1. Store the action or reusable workflow in a private repository. For more information, see [AUTOTITLE](/repositories/creating-and-mana... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/share-with-your-organization.md | main | github-actions | [
-0.07553040981292725,
-0.03503894433379173,
-0.07348974794149399,
0.04111946001648903,
0.011794153600931168,
0.08161908388137817,
0.10018360614776611,
-0.016601894050836563,
-0.04093972221016884,
0.02100147120654583,
0.047741908580064774,
-0.019579436630010605,
0.016407325863838196,
-0.045... | 0.111494 |
## Creating a reusable workflow Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported. {% ifversion ghec or ghes... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/reuse-workflows.md | main | github-actions | [
-0.023958666250109673,
-0.06659288704395294,
-0.03808062523603439,
0.046200599521398544,
0.023337846621870995,
-0.01668010838329792,
-0.037483274936676025,
-0.02489703707396984,
0.04125786945223808,
-0.05220052972435951,
-0.037457242608070374,
0.06600794941186905,
-0.0052337865345180035,
-... | 0.137945 |
main jobs: call-workflow: uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 call-workflow-passing-data: permissions: contents: read pull-requests: write uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main with: config-path: .github/labeler.yml secrets: token: ${{ secrets.GITHUB\_TOKEN }} ```... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/reuse-workflows.md | main | github-actions | [
-0.08692119270563126,
-0.04616818204522133,
-0.12070939689874649,
0.023711690679192543,
-0.026689039543271065,
-0.027855167165398598,
0.019510578364133835,
-0.02756447158753872,
-0.0018131451215595007,
-0.06946945935487747,
-0.000956604431848973,
0.04896943271160126,
-0.0023054522462189198,
... | 0.150662 |
completing reusable workflow of the matrix which actually sets a value. That means if the last successful completing reusable workflow sets an empty string for its output, and the second last successful completing reusable workflow sets an actual value for its output, the output will contain the value of the second las... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/reuse-workflows.md | main | github-actions | [
-0.07066026329994202,
-0.0008434628834947944,
-0.06731031090021133,
0.03461632877588272,
-0.07040014863014221,
0.009137541987001896,
0.0173567496240139,
-0.04965522885322571,
0.025387458503246307,
-0.05878107622265816,
0.009468463249504566,
-0.015076548792421818,
0.03665217384696007,
-0.05... | 0.053111 |
items in the array are in the reverse order that they were called in. For example, in a chain of workflows A > B > C, when viewing the logs for a job in workflow C, the array would be `["octo-org/octo-repo/.github/workflows/B.yml", "octo-org/octo-repo/.github/workflows/A.yml"]`. \* `calling\_workflow\_shas` - an array ... | https://github.com/github/docs/blob/main/content/actions/how-tos/reuse-automations/reuse-workflows.md | main | github-actions | [
-0.05158626288175583,
0.029446544125676155,
-0.05443808436393738,
-0.01735975407063961,
0.018682552501559258,
-0.06428039819002151,
0.058902449905872345,
-0.09219489246606827,
0.11931253969669342,
-0.05243297293782234,
-0.030754035338759422,
0.06639835238456726,
-0.014139250852167606,
-0.0... | 0.146874 |
When a job's `if` condition is evaluated, {% data variables.product.prodname\_actions %} logs the expression evaluation to help you understand the result. This is useful for debugging both why a job was skipped and why a job ran when you expected it to be skipped. ## Accessing expression logs 1. Navigate to the workflo... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/view-job-condition-logs.md | main | github-actions | [
-0.06470818817615509,
0.05326947197318077,
-0.0438695102930069,
0.04122171178460121,
0.07509277015924454,
-0.058573417365550995,
0.06378282606601715,
-0.04567693546414375,
0.025526592507958412,
-0.019998595118522644,
0.06403301656246185,
-0.027972960844635963,
0.01188557967543602,
-0.06986... | 0.061914 |
{% data reusables.actions.enterprise-github-hosted-runners %} You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname\_dotcom %} account to view workflow run information, including for public repositories. For more informati... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/use-workflow-run-logs.md | main | github-actions | [
0.009843803010880947,
-0.051615696400403976,
-0.07648597657680511,
0.015005174092948437,
0.07551837712526321,
-0.04821666702628136,
-0.0011035094503313303,
-0.005191138479858637,
-0.003813548246398568,
-0.008109519258141518,
-0.027001885697245598,
0.02801322750747204,
-0.006000474561005831,
... | 0.103149 |
the previous run attempts that ran the other jobs. ## Deleting logs You can delete the log files from your workflow runs through the {% data variables.product.prodname\_dotcom %} web interface or programmatically. {% data reusables.repositories.permissions-statement-write %} ### Deleting logs via the {% data variables.... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/use-workflow-run-logs.md | main | github-actions | [
-0.05164933577179909,
-0.03825691342353821,
-0.018943365663290024,
0.012184377759695053,
0.036283936351537704,
-0.050813641399145126,
0.029441500082612038,
-0.09014110267162323,
-0.04772801697254181,
0.0018331902101635933,
-0.010523702017962933,
0.022483723238110542,
-0.025896945968270302,
... | 0.078584 |
that contain the word `error`. ```shell gh run view --job JOB\_ID --log | grep error ``` To filter the logs for any failed steps, use `--log-failed` instead of `--log`. ```shell gh run view --job JOB\_ID --log-failed ``` | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/use-workflow-run-logs.md | main | github-actions | [
0.005460955668240786,
0.016206888481974602,
-0.010666830465197563,
-0.025648342445492744,
0.06263280659914017,
-0.026769300922751427,
0.04493577405810356,
-0.02516808919608593,
-0.050431787967681885,
0.0021262094378471375,
0.0020300073083490133,
-0.1041623055934906,
0.019350998103618622,
0... | -0.008622 |
{% data reusables.actions.enterprise-github-hosted-runners %} > [!NOTE] > Workflow badges in a private repository are not accessible externally, so you won't be able to embed them or link to them from an external site. {% data reusables.repositories.actions-workflow-status-badge-intro %} To add a workflow status badge ... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/add-a-status-badge.md | main | github-actions | [
-0.038791634142398834,
0.04138527065515518,
-0.06451122462749481,
0.060423582792282104,
0.05482937768101692,
0.04449174553155899,
-0.03722885251045227,
0.031102914363145828,
-0.0072602033615112305,
-0.015519795939326286,
-0.04886813834309578,
0.08789531886577606,
0.07854153215885162,
-0.00... | 0.077376 |
{% data reusables.actions.enterprise-github-hosted-runners %} Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname\_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/view-job-execution-time.md | main | github-actions | [
-0.0072166575118899345,
-0.017827069386839867,
-0.07293672859668732,
0.07877255231142044,
0.032708872109651566,
-0.005640807095915079,
-0.020278511568903923,
-0.00032377225579693913,
-0.013081610202789307,
0.019869262352585793,
0.008265739306807518,
0.005480313673615456,
-0.04140772670507431... | 0.078786 |
{% data reusables.actions.enterprise-github-hosted-runners %} These extra logs are enabled by setting secrets or variables in the repository containing the workflow, so the same permissions requirements will apply: \* {% data reusables.actions.permissions-statement-secrets-variables-repository %} \* {% data reusables.a... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/enable-debug-logging.md | main | github-actions | [
-0.001528189517557621,
-0.04393333941698074,
-0.05854716897010803,
0.062391024082899094,
0.055762551724910736,
-0.015715792775154114,
0.011196833103895187,
-0.03600405901670456,
-0.025064796209335327,
-0.004675221163779497,
0.0034058631863445044,
0.04022097960114479,
0.002150741871446371,
... | 0.127071 |
{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.permissions-statement-read %} {% webui %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.vi... | https://github.com/github/docs/blob/main/content/actions/how-tos/monitor-workflows/view-workflow-run-history.md | main | github-actions | [
0.008608276955783367,
-0.06784946471452713,
-0.04253440350294113,
0.027856409549713135,
0.024045350030064583,
-0.048788320273160934,
0.022391820326447487,
-0.030481429770588875,
-0.05361390858888626,
-0.006653566844761372,
-0.00373975932598114,
0.02642633579671383,
0.010924657806754112,
-0... | 0.057815 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction After you create an action, you'll want to continue releasing new features while working with community contributions. This tutorial describes an example process you can follow to release and maintain actions in open source. The example: \* L... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/release-and-maintain-actions.md | main | github-actions | [
-0.0677424743771553,
-0.06647808849811554,
-0.06722849607467651,
0.04305952042341232,
0.05840503051877022,
0.027025798335671425,
0.032709747552871704,
0.08838936686515808,
-0.056071896106004715,
0.017151663079857826,
0.03861808031797409,
0.02314373292028904,
-0.002500203438103199,
-0.02425... | 0.176007 |
or other workflows triggered upon pull request require access to secrets, consider using a different event like a [manual trigger](/actions/using-workflows/events-that-trigger-workflows#manual-events) or a [`pull\_request\_target`](/actions/using-workflows/events-that-trigger-workflows#pull\_request\_target). For more ... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/release-and-maintain-actions.md | main | github-actions | [
-0.029998911544680595,
-0.03725091740489006,
-0.05630269646644592,
-0.04532593488693237,
0.020522357895970345,
0.006092562340199947,
0.021362312138080597,
0.030478259548544884,
-0.014641582034528255,
0.004981507081538439,
0.03631921857595444,
-0.028028560802340508,
-0.01734323799610138,
-0... | 0.040255 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## About exit codes {% data variables.product.prodname\_dotcom %} uses the exit code to set the action's check run status, which can be `success` or `failure`. Exit status | Check run status | Description ------------|------------------|------------ `0` | `s... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/set-exit-codes.md | main | github-actions | [
-0.040766697376966476,
-0.04537731036543846,
-0.083894282579422,
0.015726745128631592,
0.05301321670413017,
-0.0005725238006561995,
0.056943390518426895,
0.04267556220293045,
-0.018337126821279526,
0.056700222194194794,
0.06551207602024078,
0.043374720960855484,
0.024909481406211853,
-0.06... | 0.183181 |
If you enable immutable releases on your action's repository, you can manage your action's releases as follows: 1. To start the release cycle, develop and validate a potential release for your action on a release branch. 1. Determine how you want to share your changes: \* If you are ready to share an unchangeable versi... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/using-immutable-releases-and-tags-to-manage-your-actions-releases.md | main | github-actions | [
-0.004771333187818527,
-0.07762005180120468,
-0.027026472613215446,
-0.02268964610993862,
0.010558835230767727,
0.038310445845127106,
0.014505812898278236,
0.02043052949011326,
-0.023136543110013008,
0.050743307918310165,
0.07895125448703766,
0.06518443673849106,
0.007395189255475998,
0.00... | 0.000674 |
## Prerequisites >[!NOTE] > You must accept the terms of service to publish actions in {% data variables.product.prodname\_marketplace %}. Before you can publish an action, you'll need to create an action in your repository. For more information, see [AUTOTITLE](/actions/creating-actions). When you plan to publish your... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/publish-in-github-marketplace.md | main | github-actions | [
-0.038273416459560394,
-0.04330391064286232,
-0.10535354167222977,
0.01374517660588026,
-0.01854342222213745,
0.03209983557462692,
0.08034713566303253,
0.06561704725027084,
-0.1204114630818367,
0.09552954882383347,
0.08442177623510361,
-0.03850938379764557,
0.03570556640625,
0.017353996634... | 0.045606 |
all other fields and click \*\*Publish release\*\*. Publishing requires you to use two-factor authentication. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication). ## Removing an action from {% data variables.product.prodna... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/publish-in-github-marketplace.md | main | github-actions | [
0.027482911944389343,
0.015254538506269455,
-0.06241941079497337,
0.050413019955158234,
0.01730462722480297,
0.02965524233877659,
0.06240752339363098,
-0.02715776301920414,
-0.07784377038478851,
0.11725454777479172,
0.10432683676481247,
-0.01747678592801094,
0.03697726130485535,
-0.0188000... | -0.025373 |
## Choosing a location for your action If you're developing an action for other people to use, we recommend keeping the action in its own repository instead of bundling it with other application code. This allows you to version, track, and release the action just like any other software. {% ifversion fpt or ghec %} Sto... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/manage-custom-actions.md | main | github-actions | [
-0.05963537469506264,
-0.06907287985086441,
-0.0666041150689125,
-0.02696496993303299,
0.0838334709405899,
0.04785863682627678,
0.05766356736421585,
0.115192711353302,
-0.03646232932806015,
0.08266659080982208,
0.07601220905780792,
0.07709375023841858,
-0.021405940875411034,
-0.01847365498... | 0.117539 |
will break existing workflows, such as changing an action's inputs. #### Syntax for referencing tags This example demonstrates how a user can reference a major version tag: ```yaml steps: - uses: actions/javascript-action@v1 ``` This example demonstrates how a user can reference a specific patch release tag: ```yaml st... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/manage-custom-actions.md | main | github-actions | [
-0.06893523782491684,
-0.051843900233507156,
0.050180889666080475,
-0.025091135874390602,
0.020642677322030067,
-0.007284202147275209,
0.026005439460277557,
-0.0015639225021004677,
0.08477328717708588,
0.02195107378065586,
-0.0010812862310558558,
0.060541003942489624,
-0.033305030316114426,
... | 0.071936 |
## Introduction You can write an action to provide a way for users to access your servers via a configured CLI environment on {% data variables.product.prodname\_actions %} runners. Your action should: \* Make it simple for users to specify the version of the CLI to install \* Support multiple operating systems \* Run ... | https://github.com/github/docs/blob/main/content/actions/how-tos/create-and-publish-actions/create-a-cli-action.md | main | github-actions | [
0.045975200831890106,
-0.07640708982944489,
-0.05095065385103226,
-0.04113082215189934,
0.019196219742298126,
-0.010251852683722973,
0.014385752379894257,
0.06994400918483734,
-0.045426446944475174,
-0.004653050564229488,
0.01198495365679264,
0.01368290837854147,
0.02328130416572094,
-0.02... | 0.055675 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Configuring a workflow to run manually To run a workflow manually, the workflow must be configured to run on the `workflow\_dispatch` event. To trigger the `workflow\_dispatch` event, your workflow must be in the default branch. For more information about... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/manually-run-a-workflow.md | main | github-actions | [
-0.014093202538788319,
-0.112046979367733,
-0.01726660504937172,
0.05836517736315727,
-0.014997581019997597,
-0.06807653605937958,
-0.0017471567261964083,
-0.03743261843919754,
-0.02327224798500538,
-0.02063455805182457,
-0.005474310368299484,
0.008460641838610172,
0.002228918019682169,
0.... | 0.078758 |
Re-runs use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. The workflow will also use the same `GITHUB\_SHA` (commit SHA) and `GITHUB\_REF` (git ref) of the original event that triggered the workflow run. A workflow run can be re-run a maximum... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs.md | main | github-actions | [
-0.02938099205493927,
-0.08610303699970245,
0.03024369664490223,
0.018905367702245712,
-0.027881300076842308,
-0.034284915775060654,
-0.0005734704318456352,
-0.12632842361927032,
0.012077274732291698,
-0.046323128044605255,
0.015968026593327522,
0.06528768688440323,
0.033258795738220215,
-... | 0.005742 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Deleting an artifact > [!WARNING] > Once you delete an artifact, it cannot be restored. {% data reusables.repositories.permissions-statement-write %} {% data reusables.actions.artifact-log-retention-statement %} {% data reusables.repositories.navigate-to-... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/remove-workflow-artifacts.md | main | github-actions | [
-0.031121594831347466,
0.015952114015817642,
0.008408288471400738,
0.03593217954039574,
0.035806283354759216,
-0.08554953336715698,
0.024409476667642593,
-0.14168894290924072,
0.04419213533401489,
-0.008851519785821438,
-0.0007497822516597807,
0.039881765842437744,
0.029335135594010353,
-0... | 0.09559 |
{% data reusables.actions.enterprise-github-hosted-runners %} Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname\_dotcom %}. Temporarily disabling a workflow can be use... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/disable-and-enable-workflows.md | main | github-actions | [
-0.04709353297948837,
0.016982685774564743,
-0.018459590151906013,
0.016891922801733017,
0.06382235884666443,
-0.008148453198373318,
0.0051514445804059505,
-0.01591366156935692,
0.02232424169778824,
-0.013541797176003456,
-0.00980382040143013,
0.09322544187307358,
0.013109803199768066,
-0.... | 0.181649 |
Workflow runs triggered by a contributor's pull request from a fork may require manual approval from a maintainer with write access. You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-act... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/approve-runs-from-forks.md | main | github-actions | [
-0.0024381056427955627,
-0.09360317885875702,
0.026698077097535133,
-0.04224889352917671,
0.05028953030705452,
-0.059927988797426224,
-0.046103037893772125,
-0.06655958294868469,
0.03837479650974274,
0.04200604185461998,
-0.0002072179486276582,
0.013617782853543758,
-0.016980890184640884,
... | 0.062531 |
{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.repositories.permissions-statement-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} 1. To delete a workflow run, select {% octic... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/delete-a-workflow-run.md | main | github-actions | [
-0.01706518791615963,
-0.018200300633907318,
-0.041103851050138474,
0.029765833169221878,
0.008095606230199337,
-0.028929077088832855,
0.0027216074522584677,
-0.14322377741336823,
0.06598889082670212,
-0.03786307945847511,
-0.02874315157532692,
0.056035034358501434,
0.009461507201194763,
-... | 0.095135 |
{% data reusables.actions.enterprise-github-hosted-runners %} By default, {% data variables.product.github %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-setti... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/download-workflow-artifacts.md | main | github-actions | [
-0.023950785398483276,
-0.043402865529060364,
-0.03239217400550842,
0.05376868695020676,
0.02818397618830204,
-0.017755981534719467,
0.02602492831647396,
-0.05551636219024658,
-0.004354089964181185,
0.02275879494845867,
0.03236052393913269,
0.036286860704422,
0.02555745095014572,
0.0215877... | 0.063765 |
{% data reusables.actions.enterprise-github-hosted-runners %} > [!NOTE] > If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull\_requestpull\_request\_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-action... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/skip-workflow-runs.md | main | github-actions | [
0.00042112136725336313,
-0.05606740713119507,
-0.008594484999775887,
0.027406636625528336,
0.04331635311245918,
-0.06556873023509979,
0.0062223463319242,
-0.06815101951360703,
0.047666996717453,
-0.01788421720266342,
0.0203504990786314,
0.042491987347602844,
0.01975134015083313,
-0.0679606... | 0.082692 |
## Canceling a workflow run {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} 1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel. 1. In the upper-right corner... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/cancel-a-workflow-run.md | main | github-actions | [
-0.05871155858039856,
0.03369845822453499,
0.005211313255131245,
0.01566225476562977,
0.025561083108186722,
-0.04305826872587204,
0.11866673827171326,
-0.13048695027828217,
0.024332020431756973,
0.024610377848148346,
-0.007055769674479961,
0.05345439538359642,
0.0004726778715848923,
-0.075... | 0.074676 |
This article describes managing caches with the {% data variables.product.prodname\_dotcom %} web interface, but you can also manage them: \* Using the REST API. See [AUTOTITLE](/rest/actions/cache). \* With the `gh cache` subcommand from the command line. See the [GitHub CLI documentation](https://cli.github.com/manua... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/manage-caches.md | main | github-actions | [
0.005493540316820145,
-0.024894285947084427,
-0.060782209038734436,
-0.02811279334127903,
0.01837206445634365,
-0.035276148468256,
0.07075140625238419,
0.022415993735194206,
-0.016903169453144073,
0.03131181746721268,
0.021609647199511528,
0.03606845438480377,
0.0014624864561483264,
-0.071... | 0.104502 |
raw %}${{ github.token }}{% endraw %} GH\_REPO: {% raw %}${{ github.repository }}{% endraw %} BRANCH: refs/pull/{% raw %}${{ github.event.pull\_request.number }}{% endraw %}/merge ``` Alternatively, you can use the API to automatically list or delete all caches on your own cadence. For more information, see [AUTOTITLE]... | https://github.com/github/docs/blob/main/content/actions/how-tos/manage-workflow-runs/manage-caches.md | main | github-actions | [
-0.004467599559575319,
-0.0026415076572448015,
-0.017811138182878494,
-0.007145437877625227,
0.03665206953883171,
0.0038935085758566856,
0.006469291169196367,
-0.0063668349757790565,
0.0677938312292099,
0.02201305888593197,
-0.01603061333298683,
0.027037115767598152,
-0.02649409882724285,
... | 0.062113 |
You may be rate limited by {% data variables.product.prodname\_actions %} when you scale your usage. Some limits can be increased by contacting {% data variables.contact.contact\_support %}. Unless otherwise stated, the expected behavior when a limit is reached is that the workflow/job will get cancelled. These limits ... | https://github.com/github/docs/blob/main/content/actions/reference/limits.md | main | github-actions | [
-0.03508119657635689,
-0.04193342849612236,
-0.044914569705724716,
0.021953795105218887,
0.030122237280011177,
-0.08019513636827469,
-0.010130773298442364,
0.039439354091882706,
0.00027242081705480814,
0.014214124530553818,
0.06691936403512955,
0.00181751255877316,
-0.009341074153780937,
-... | 0.083552 |
time | 5 days | Each job in a workflow can run for up to 5 days of execution time. If a job reaches this limit, the job is terminated and fails. | {% octicon "x" aria-label="No" %} | | Self-hosted | Job queue time | 24 hours | A job can be in the queue for 24 hours before it is automatically cancelled. | {% octicon "x"... | https://github.com/github/docs/blob/main/content/actions/reference/limits.md | main | github-actions | [
-0.03244325518608093,
-0.01904023066163063,
-0.06994342803955078,
0.059889014810323715,
0.01117075327783823,
-0.06381610035896301,
-0.0405934639275074,
-0.04164181277155876,
-0.014219224452972412,
-0.036976225674152374,
0.011586000211536884,
0.05652792379260063,
0.03473727032542229,
-0.063... | 0.117019 |
Standard {% data variables.product.github %}-hosted runner | Pro | 40 | 5 | Not applicable | | Standard {% data variables.product.github %}-hosted runner | Team | 60 | 5 | Not applicable | | Standard {% data variables.product.github %}-hosted runner | Enterprise | 500 | 50 | Not applicable | | Larger runner | Team | 10... | https://github.com/github/docs/blob/main/content/actions/reference/limits.md | main | github-actions | [
0.0302630253136158,
-0.017920253798365593,
-0.09144973754882812,
0.019635068252682686,
0.007208114489912987,
-0.06527744233608246,
-0.031182195991277695,
0.03117271512746811,
-0.043167028576135635,
0.06094161793589592,
-0.0026327187661081553,
0.06523199379444122,
0.009546737186610699,
-0.0... | 0.078418 |
## Naming your secrets >[!TIP] > To help ensure that {% data variables.product.prodname\_dotcom %} redacts your secrets in logs correctly, avoid using structured data as the values of secrets. The following rules apply to secret names: {% data reusables.actions.actions-secrets-and-variables-naming %} {% data reusables.... | https://github.com/github/docs/blob/main/content/actions/reference/security/secrets.md | main | github-actions | [
-0.05453440174460411,
-0.03701518476009369,
-0.0992870107293129,
0.005431422032415867,
0.006885360926389694,
-0.031253665685653687,
0.010591544210910797,
0.03117186948657036,
0.0007040803320705891,
0.03495260700583458,
-0.0012715688208118081,
0.021051762625575066,
0.06396514177322388,
-0.0... | 0.104249 |
## OIDC token claims To see all the claims supported by {% data variables.product.prodname\_dotcom %}'s OIDC provider, review the `claims\_supported` entries at {% ifversion ghes %}`https://HOSTNAME/\_services/token/.well-known/openid-configuration`{% else %}https://token.actions.githubusercontent.com/.well-known/openi... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.08789761364459991,
0.011655404232442379,
-0.07795147597789764,
0.06648541986942291,
0.08494304865598679,
-0.04499959573149681,
0.06613118946552277,
0.06343268603086472,
-0.012457015924155712,
0.042219553142786026,
0.0021330935414880514,
-0.04231848940253258,
0.0350043959915638,
-0.03123... | 0.120682 |
or `public`. | | `repository`| The repository from where the workflow is running. | | `repository\_id`| The ID of the repository from where the workflow is running. | | `repository\_owner`| The name of the organization in which the `repository` is stored. | | `repository\_owner\_id`| The ID of the organization in which... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.07081439346075058,
-0.00808824971318245,
-0.09889288991689682,
0.07052870839834213,
0.020613830536603928,
-0.07406186312437057,
0.05939605459570885,
-0.002532106824219227,
0.09328269213438034,
-0.01084674708545208,
-0.009362556040287018,
-0.017848756164312363,
0.021384255960583687,
-0.0... | 0.121422 |
subject claims The following examples demonstrate how to use "Subject" as a condition, and explain how the "Subject" is assembled from concatenated metadata. The [subject](https://openid.net/specs/openid-connect-core-1\_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/conte... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.018781054764986038,
0.0310604739934206,
0.002264865906909108,
-0.0019872330594807863,
0.09211317449808121,
-0.08356204628944397,
0.045349277555942535,
-0.04971598461270332,
0.08366666734218597,
0.0012183566577732563,
-0.09485770761966705,
-0.10626731067895889,
0.03848567605018616,
0.071... | 0.147045 |
can security harden your OIDC configuration by customizing the claims that are included with the JWT. These customizations allow you to define more granular trust conditions on your cloud roles when allowing your workflows to access resources hosted in the cloud: \* You can customize values for {% ifversion ghec %}`iss... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.1147589161992073,
0.03487598896026611,
-0.009567609056830406,
0.03850582242012024,
0.06235721334815025,
-0.03492650389671326,
0.04426160827279091,
-0.01816149428486824,
0.044480565935373306,
-0.0770406723022461,
-0.07408467680215836,
0.007599296048283577,
0.06662533432245255,
-0.0684280... | 0.058797 |
select repository custom properties to include as claims in {% data variables.product.prodname\_actions %} OIDC tokens. Once a custom property is added to the OIDC configuration, every repository in the organization or enterprise that has a value set for that property will automatically include it in its OIDC tokens. T... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.09227312356233597,
0.012764278799295425,
-0.05389674752950668,
0.06921599805355072,
-0.021499456837773323,
0.013710277155041695,
0.11862985044717789,
-0.01321150828152895,
0.038697339594364166,
0.06786388158798218,
0.03888002783060074,
-0.0796157717704773,
0.09251491725444794,
0.0139418... | 0.021982 |
included in the token: ```json { "sub": "repo:my-org/my-repo:ref:refs/heads/main", "aud": "https://github.com/my-org", "repository": "my-org/my-repo", "repo\_property\_business\_unit": "payments", "repo\_property\_workspace\_id": "ws-abc123" } ``` You can use these `repo\_property\_\*` claims as conditions in your clou... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.10997427999973297,
0.03178561106324196,
0.027379116043448448,
0.011517785489559174,
-0.012492387555539608,
0.005552320275455713,
0.057741113007068634,
-0.07129330188035965,
0.05959812179207802,
0.01793745905160904,
-0.008094513788819313,
-0.04927152022719383,
0.07847695052623749,
0.0448... | 0.003481 |
specific owner This example template enables the `sub` claim to have a new format with only the value of `repository\_owner`. {% data reusables.actions.use-request-body-api %} ```json { "include\_claim\_keys": [ "repository\_owner" ] } ``` In your cloud provider's OIDC configuration, configure the `sub` condition to re... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.13066062331199646,
0.04998551681637764,
0.039526619017124176,
0.019356129691004753,
-0.005304817110300064,
-0.024318912997841835,
0.029258709400892258,
-0.018844017758965492,
0.05366407707333565,
0.008865135721862316,
-0.020821500569581985,
-0.04121493175625801,
0.028838537633419037,
0.... | 0.015606 |
in the token. {% data reusables.actions.use-request-body-api %} ```json { "include\_claim\_keys": [ "repo\_property\_workspace\_id" ] } ``` In your cloud provider's OIDC configuration, configure the `sub` condition to require that claims must include a specific value for `repo\_property\_workspace\_id`. For example: `"... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.10738853365182877,
0.06619338691234589,
0.02078484557569027,
0.07800158858299255,
0.020437246188521385,
-0.0006710683228448033,
0.03344416990876198,
-0.029246438294649124,
0.052926793694496155,
0.05740002915263176,
0.021389149129390717,
-0.015743978321552277,
0.029935281723737717,
0.046... | -0.001958 |
token Custom actions can request the OIDC token using: \* The `getIDToken()` method from the Actions toolkit. For more information, see [OIDC Token](https://www.npmjs.com/package/@actions/core/v/1.6.0#oidc-token) in the npm package documentation. \* The following environment variables on the runner. | Variable | Descri... | https://github.com/github/docs/blob/main/content/actions/reference/security/oidc.md | main | github-actions | [
-0.07500652968883514,
0.012700382620096207,
-0.04916924983263016,
0.02555803395807743,
0.03477108106017113,
-0.0017964172875508666,
0.06439755111932755,
0.09107302129268646,
0.036004576832056046,
0.06739931553602219,
-0.028965698555111885,
-0.03366831690073013,
-0.04141401872038841,
-0.039... | 0.141211 |
Find information about security best practices when you are writing workflows and using {% data variables.product.prodname\_actions %} security features. ## Writing workflows ### Use secrets for sensitive information Because there are multiple ways a secret value can be transformed, automatic redaction is not guarantee... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.06105918809771538,
-0.019838374108076096,
-0.09449564665555954,
-0.020240213721990585,
-0.04271644353866577,
0.03936448320746422,
0.07378525286912918,
0.09506901353597641,
0.013265572488307953,
-0.0031606184784322977,
0.0019239626126363873,
0.013115606270730495,
0.03900476545095444,
0.0... | 0.098359 |
secrets are properly redacted, or not shown. It's not always obvious how a command or tool you’re invoking will send errors to `STDOUT` and `STDERR`, and secrets might subsequently end up in error logs. As a result, it is good practice to manually review the workflow logs after testing valid and invalid inputs. For inf... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.038945771753787994,
0.032092273235321045,
-0.05018119886517525,
0.04332839325070381,
0.025171179324388504,
-0.045319054275751114,
-0.014332926832139492,
-0.0641709640622139,
0.052551623433828354,
0.007467744406312704,
-0.017444605007767677,
-0.02571968175470829,
0.018146727234125137,
0.... | 0.021577 |
For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github\_token). {% ifversion custom-org-roles %} ## Mitigating the risks of untrusted code checkout Similar to script injection attacks, untrusted pull request content that automatically trigg... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.08065403252840042,
-0.0006890534423291683,
-0.04714502766728401,
-0.012743071652948856,
0.04384895786643028,
-0.007072190288454294,
0.029728515073657036,
0.028878239914774895,
0.06574983149766922,
-0.01702461764216423,
-0.022438419982790947,
0.012021400034427643,
0.025550713762640953,
-... | 0.174372 |
the {% ifversion ghec or ghes %}repository, organization, and enterprise{% else %}repository and organization{% endif %} level to require actions to be pinned to a full-length commit SHA: \* To configure the policy at the repository level, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/en... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
0.018139908090233803,
-0.042796723544597626,
-0.047533247619867325,
-0.031203895807266235,
0.01598404534161091,
0.0217243954539299,
-0.014080732129514217,
-0.05259321257472038,
-0.007579002995043993,
0.06661449372768402,
0.04942082241177559,
-0.011933750472962856,
-0.007562435697764158,
0.... | 0.075737 |
data reusables.actions.dependabot-version-updates-for-actions %} {% ifversion ghec or ghes %} ### Allowing workflows to access internal and private repositories {% data reusables.actions.outside-collaborators-actions %} For more information, see [AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-y... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.11759253591299057,
-0.05887342989444733,
0.027224162593483925,
-0.04819762706756592,
0.0005350979627110064,
0.047120291739702225,
0.04168444126844406,
0.008400192484259605,
0.015576458536088467,
0.04552874714136124,
0.027581535279750824,
0.02254103124141693,
-0.03751455619931221,
-0.000... | 0.034845 |
{% data variables.product.github %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (gener... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.039608098566532135,
-0.021857837215065956,
-0.034241147339344025,
0.06069600209593773,
0.03482569754123688,
-0.029901929199695587,
-0.011639934033155441,
0.04994269832968712,
0.019002730026841164,
-0.03239426389336586,
-0.004220784641802311,
0.041883863508701324,
0.04458124190568924,
-0... | 0.145033 |
single location to view and manage your runners. \* If you only have a single organization, then adding your runners at the organization level is effectively the same approach, but you might encounter difficulties if you add another organization in the future. \*\*Decentralized management:\*\* \* If each team will mana... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
0.0016784834442660213,
-0.07394745200872421,
-0.09249136596918106,
-0.006540287286043167,
0.01702168770134449,
0.02715585194528103,
-0.06283777952194214,
0.03857915475964546,
0.02599966712296009,
0.014757951721549034,
0.017322778701782227,
0.008741491474211216,
0.04159512743353844,
0.01383... | 0.120823 |
{% data variables.product.prodname\_advisory\_database %}. You can search the database for actions that you use to find information about existing vulnerabilities and instructions for how to fix them. To streamline your search, use the {% data variables.product.prodname\_actions %} filter in the [{% data variables.prod... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.0061697629280388355,
-0.01932392828166485,
-0.0945611372590065,
0.06559421122074127,
0.07301247119903564,
-0.008955256082117558,
0.0557047575712204,
0.04492595046758652,
-0.04450152814388275,
-0.003617512760683894,
-0.010732983238995075,
-0.01392978336662054,
0.060209326446056366,
-0.01... | 0.091102 |
you've published. \* Use the dependants view in the Dependency graph to see which projects depend on your code. If you receive a vulnerability report, this will give you an idea of who you need to communicate with about the vulnerability and how to fix it. For more information, see [AUTOTITLE](/code-security/supply-cha... | https://github.com/github/docs/blob/main/content/actions/reference/security/secure-use.md | main | github-actions | [
-0.09817356616258621,
-0.0005198396393097937,
-0.026203114539384842,
0.020256750285625458,
0.030688704922795296,
0.02594180777668953,
-0.033936984837055206,
0.04882410913705826,
-0.0715775415301323,
-0.005861814133822918,
0.006550810765475035,
-0.03521811589598656,
0.039269447326660156,
0.... | 0.081408 |
## Reusable workflows Reference information for reusable workflows. ### Access to reusable workflows A reusable workflow can be used by another workflow if any of the following is true: \* Both workflows are in the same repository. \* The called workflow is stored in a public repository{% ifversion ghes %} on {% data v... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md | main | github-actions | [
-0.018193254247307777,
-0.06569285690784454,
-0.03728114068508148,
-0.023050589486956596,
0.022978898137807846,
0.029232017695903778,
0.08350472152233124,
0.011315048672258854,
-0.05612671747803688,
-0.01720932498574257,
0.01757093332707882,
0.008911236189305782,
0.015033308416604996,
0.00... | 0.059996 |
jobs that call a reusable workflow When you call a reusable workflow, you can only use the following keywords in the job containing the call: \* [`jobs..name`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob\_idname) \* [`jobs..uses`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsj... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md | main | github-actions | [
-0.08470291644334793,
-0.054880764335393906,
-0.01694260537624359,
0.009791962802410126,
0.024450747296214104,
-0.02121485210955143,
0.09159611910581589,
-0.09834680706262589,
-0.0033348649740219116,
-0.060187432914972305,
-0.012181829661130905,
0.05046281963586807,
0.04896236211061478,
0.... | 0.071338 |
private `.github` repository are only available to private repositories. {% ifversion ghec %} Because public workflow templates require a public `.github` repository, they are not available for {% data variables.product.prodname\_emus %}. {% endif %} ### Granting access for private/internal repositories If you're using... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md | main | github-actions | [
0.034913353621959686,
-0.012986469082534313,
-0.07033159583806992,
-0.030293671414256096,
0.031119924038648605,
0.01796003244817257,
-0.005011436995118856,
0.0846288874745369,
0.05985270440578461,
-0.015400371514260769,
0.014454779215157032,
-0.01235368475317955,
-0.01230140496045351,
-0.0... | 0.073225 |
{% data reusables.actions.enterprise-github-hosted-runners %} ### USER Docker actions must be run by the default Docker user (root). Do not use the `USER` instruction in your `Dockerfile`, because you won't be able to access the `GITHUB\_WORKSPACE` directory. For more information, see [AUTOTITLE](/actions/reference/var... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/dockerfile-support.md | main | github-actions | [
0.01356346532702446,
0.0023441410157829523,
-0.01699199341237545,
0.01655976101756096,
0.02602081187069416,
-0.05003492906689644,
-0.013477331958711147,
0.06032547354698181,
-0.02501142956316471,
0.032146427780389786,
-0.05057036131620407,
-0.016106000170111656,
0.04427739605307579,
-0.008... | -0.003112 |
'%d args:' "$#" printf " '%s'" "$@" printf '\n' ``` Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command: ```shell chmod +x entrypoint.sh ``` When an `ENTRYPOINT` shell script is not ... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/dockerfile-support.md | main | github-actions | [
0.04926181957125664,
0.01848651096224785,
-0.07613416761159897,
-0.0619044154882431,
-0.010464520193636417,
-0.0678020790219307,
0.0459478385746479,
0.06227948144078255,
0.024274252355098724,
0.006682414561510086,
-0.05242137983441353,
-0.05439319461584091,
0.04890318587422371,
0.049251053... | 0.054719 |
## Available contexts | Context name | Type | Description | |---------------|------|-------------| | `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). | | `env` | `object` | Contains variables set in a workflow, job, or step. For more information, s... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/contexts.md | main | github-actions | [
-0.024083318188786507,
-0.028760062530636787,
-0.08697772771120071,
0.060876209288835526,
0.058728475123643875,
-0.05822982266545296,
0.05367672070860863,
-0.020562874153256416,
-0.02241457626223564,
-0.05482902005314827,
-0.05415183678269386,
0.008307201787829399,
0.05333308130502701,
-0.... | 0.129402 |
on branch $GITHUB\_REF" ``` {% endraw %} In this example, the `if` statement checks the [`github.ref`](/actions/learn-github-actions/contexts#github-context) context to determine the current branch name; if the name is `refs/heads/main`, then the subsequent steps are executed. The `if` check is processed by {% data var... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/contexts.md | main | github-actions | [
-0.02572164684534073,
-0.017958352342247963,
-0.07525794953107834,
-0.005292157642543316,
0.10372547805309296,
-0.025670411065220833,
0.02788121998310089,
-0.003959506284445524,
0.03727864846587181,
-0.003484137589111924,
0.033547475934028625,
0.022632034495472908,
0.036811232566833496,
-0... | 0.118284 |
matrix, job, runner, env, vars, secrets, steps, inputs` | `hashFiles` | | `jobs..steps.with` | `github, needs, strategy, matrix, job, runner, env, vars, secrets, steps, inputs` | `hashFiles` | | `jobs..steps.working-directory` | `github, needs, strategy, matrix, job, runner, env, vars, secrets, steps, inputs` | `hashFi... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/contexts.md | main | github-actions | [
-0.05312144756317139,
0.008627218194305897,
-0.16381199657917023,
-0.029658805578947067,
-0.022792741656303406,
-0.03354550898075104,
0.023300552740693092,
0.0470271036028862,
-0.035640470683574677,
0.021996047347784042,
0.01985577866435051,
0.02948281727731228,
0.11183338612318039,
-0.046... | 0.133751 |
| `github.actor` | `string` | The username of the user that triggered the initial workflow run. If the workflow run is a re-run, this value may differ from `github.triggering\_actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering\_actor`) has... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/contexts.md | main | github-actions | [
-0.026726672425866127,
-0.013725499622523785,
-0.0374169684946537,
-0.039769671857357025,
-0.037744294852018356,
0.030638879165053368,
0.03635947406291962,
0.02785097248852253,
0.030175000429153442,
-0.0425877720117569,
-0.014737987890839577,
-0.0174154844135046,
0.05628589540719986,
0.023... | 0.110277 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## About YAML syntax for workflows Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. {% data reusables.actions.learn-more-about-yaml %} You must store workflow files in the `.github/workflows` directory of your reposito... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.028921471908688545,
-0.08056489378213882,
-0.038672443479299545,
0.02050480619072914,
0.02096594125032425,
-0.007316499017179012,
0.05576111003756523,
0.02785218134522438,
0.04456574097275734,
-0.018073394894599915,
0.011619465425610542,
0.05356353893876076,
0.0046930015087127686,
-0.07... | 0.142099 |
`number`, or `string`. ## `on.workflow\_call.outputs` A map of outputs for a called workflow. Called workflow outputs are available to all downstream jobs in the caller workflow. Each output has an identifier, an optional `description,` and a `value.` The `value` must be set to the value of an output from a job within ... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.05728762596845627,
-0.0069100079126656055,
-0.021419065073132515,
0.010674001649022102,
-0.03981447592377663,
-0.027576450258493423,
0.029091883450746536,
-0.006283849012106657,
0.054938752204179764,
-0.08913600444793701,
-0.027025939896702766,
-0.017657935619354248,
-0.019905896857380867... | 0.079943 |
read only. ### Setting the `GITHUB\_TOKEN` permissions for all jobs in a workflow You can specify `permissions` at the top level of a workflow, so that the setting applies to all jobs in the workflow. #### Example: Setting the `GITHUB\_TOKEN` permissions for an entire workflow {% data reusables.actions.jobs.setting-per... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.042374808341264725,
-0.0694352388381958,
-0.06377292424440384,
0.005444556009024382,
-0.028994949534535408,
-0.019217338413000107,
0.05617370456457138,
0.04375138506293297,
-0.024744801223278046,
0.015873737633228302,
-0.01180166844278574,
0.04287312924861908,
0.007150289602577686,
-0.0... | 0.087927 |
data variables.product.prodname\_dotcom %} provides built-in steps to set up and complete a job. {% data variables.product.prodname\_dotcom %} only displays the first 1,000 checks, however, you can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see [AUTOTITLE... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.05157484486699104,
-0.030995400622487068,
-0.06520815938711166,
0.003981851972639561,
0.009615051560103893,
-0.06007475033402443,
-0.015182290226221085,
0.05953087657690048,
-0.06536529213190079,
-0.014178193174302578,
0.0036522599402815104,
0.022007230669260025,
0.002608947455883026,
-... | 0.151065 |
should expect to receive critical fixes and security patches while still retaining compatibility. Note that this behavior is at the discretion of the action's author. \* Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.052476733922958374,
-0.03149280324578285,
0.0097589623183012,
-0.024406250566244125,
0.051043108105659485,
-0.03579561039805412,
-0.06111585721373558,
-0.07157810032367706,
-0.03654700517654419,
0.014778628014028072,
-0.024816155433654785,
0.07259991765022278,
-0.08578205108642578,
0.00... | 0.061267 |
uses: ./.github/actions/my-private-repo/my-action ``` Alternatively, use a {% data variables.product.prodname\_github\_app %} instead of a {% data variables.product.pat\_generic %} in order to ensure your workflow continues to run even if the {% data variables.product.pat\_generic %} owner leaves. For more information,... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.06126217544078827,
-0.05470166727900505,
-0.07549464702606201,
-0.0259595587849617,
-0.01949165388941765,
-0.027461381629109383,
0.019042009487748146,
0.07925399392843246,
0.016461320221424103,
-0.019444894045591354,
0.03162335976958275,
0.03256712108850479,
0.04021944850683212,
-0.0367... | 0.088724 |
following defaults that are executed by {% data variables.product.prodname\_dotcom %}-hosted runners. You should use these guidelines when running shell scripts. \* `bash`/`sh`: \* By default, fail-fast behavior is enforced using `set -e` for both `sh` and `bash`. When `shell: bash` is specified, `-o pipefail` is also ... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
0.023997146636247635,
0.032182712107896805,
-0.05566587299108505,
0.039151858538389206,
0.036494433879852295,
0.019870854914188385,
0.012492824345827103,
0.09049656242132187,
-0.019077738747000694,
0.0534990131855011,
-0.0026225834153592587,
-0.013404306024312973,
-0.005594257265329361,
-0... | 0.053984 |
to make your action self-documenting. ## `jobs..steps[\*].with.entrypoint` Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executa... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.05772656202316284,
0.04625729098916054,
-0.011495541781187057,
0.015329464338719845,
-0.03179940581321716,
-0.03450038656592369,
-0.0009784590220078826,
0.02625068835914135,
0.031690068542957306,
-0.01045034546405077,
-0.07518196105957031,
-0.011959604918956757,
-0.02188207022845745,
0.... | 0.096055 |
value in the variable. Each job will access the `version` value through the `matrix.version` context and pass the value as `node-version` to the `actions/setup-node` action. ```yaml jobs: example\_matrix: strategy: matrix: version: [10, 12, 14] steps: - uses: {% data reusables.actions.action-setup-node %} with: node-ve... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.016957463696599007,
0.018966233357787132,
-0.07366976141929626,
0.03947021812200546,
-0.005533329211175442,
-0.03571329265832901,
-0.04985376447439194,
-0.056341156363487244,
0.0043087792582809925,
0.009355161339044571,
-0.0003019064897671342,
0.05109159275889397,
-0.011090714484453201,
... | 0.049493 |
experimental: true ``` {% endraw %} ## `jobs..container` {% data reusables.actions.docker-container-os-support %} {% data reusables.actions.jobs.section-running-jobs-in-a-container %} ## `jobs..container.image` {% data reusables.actions.jobs.section-running-jobs-in-a-container-image %} ## `jobs..container.credentials` ... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.013835117220878601,
0.01997121423482895,
-0.008559979498386383,
0.06113630160689354,
0.023930275812745094,
-0.04394795745611191,
0.0010445009684190154,
-0.03428616747260094,
-0.07905485481023788,
0.013767421245574951,
0.007254004944115877,
0.020976947620511055,
0.03688861429691315,
0.02... | 0.005355 |
Docker volumes, anonymous Docker volumes, or bind mounts on the host. To specify a volume, you specify the source and destination path: `:`. The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. ### Example of `jobs..services..volumes` ```yaml volumes: - my\_docke... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.0003893620742019266,
0.0016502863727509975,
-0.04606524109840393,
-0.010932018980383873,
-0.006026800721883774,
-0.06861468404531479,
-0.0067342109978199005,
0.018749594688415527,
0.033941108733415604,
0.005596799775958061,
-0.0300946906208992,
-0.042901020497083664,
0.037590499967336655,... | -0.025085 |
run: echo ${{ secrets.CALLING\_WORKFLOW\_SECRET }} ``` {% endraw %} ## `jobs..secrets.` A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow\_call.secrets.`](#onworkflow\_callsecretssecret\_id) in the called workflow... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.09075604379177094,
0.05203015357255936,
-0.018943626433610916,
0.028718998655676842,
0.00002908778151322622,
-0.016928592696785927,
0.04140085354447365,
-0.03923792019486427,
0.06626446545124054,
-0.040981046855449677,
-0.08389963209629059,
-0.02671017125248909,
0.004561727400869131,
-0... | 0.065028 |
match slash (`/`). The `\*` character is a special character in YAML. When you start a pattern with `\*`, you must use quotes. | `README.md` `server.rb` | | `'\*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js` `page.jsx` | | `'\*\*'` | The `\*\*` wildcard matches any character inc... | https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/workflow-syntax.md | main | github-actions | [
-0.058901913464069366,
0.004708370193839073,
0.04951580986380577,
-0.05744675174355507,
0.04647332802414894,
0.002177734160795808,
-0.032072484493255615,
0.014972923323512077,
0.0871051698923111,
0.013302765786647797,
0.004722537938505411,
0.030694840475916862,
-0.0049491929821670055,
0.05... | -0.003505 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.