content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
|:--- | :---: | :---: | :---: | Build Plan | {% octicon "check" aria-label="Required" %} | {% octicon "check" aria-label="Required" %} | {% octicon "check" aria-label="Required" %} | Deployment Project | {% octicon "check" aria-label="Required" %} | {% octicon "check" aria-label="Required" %} | {% octicon "x" aria-labe... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bamboo-migration.md | main | github-actions | [
0.013331621885299683,
0.009974286891520023,
-0.0769403800368309,
0.023247160017490387,
0.003789051901549101,
0.025241920724511147,
0.08188848197460175,
0.023834075778722763,
-0.07164514064788818,
-0.028966659680008888,
0.05895368382334709,
-0.10262156277894974,
0.039086900651454926,
-0.058... | 0.013865 |
tmp/forecast\_reports ``` ### Forecasting a project To limit the forecast to the plans and deployments environments associated with a project, you can use the `--project` option, where the value is set to a build project key. For example: ```shell gh actions-importer forecast bamboo --project PAN --output-dir tmp/forec... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bamboo-migration.md | main | github-actions | [
-0.08141817152500153,
-0.008271086029708385,
-0.08322833478450775,
0.07086861878633499,
-0.0044061061926186085,
-0.010392027907073498,
-0.021215088665485382,
0.09871850907802582,
-0.030628828331828117,
0.041973650455474854,
-0.060467373579740524,
-0.0640573501586914,
0.03696479648351669,
-... | 0.112628 |
[2022-08-20 22:08:20] Pull request: 'https://github.com/octo-org/octo-repo/pull/1' ``` ### Running the migrate command for a deployment project To migrate a Bamboo deployment project to {% data variables.product.prodname\_actions %}, run the following command in your terminal, replacing the `target-url` value with the ... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bamboo-migration.md | main | github-actions | [
-0.05749359354376793,
-0.030199898406863213,
-0.04959660395979881,
-0.032188836485147476,
0.05818617716431618,
-0.006893787067383528,
0.03184007853269577,
0.03204573690891266,
-0.06964680552482605,
0.09047640860080719,
0.06899751722812653,
-0.08700583875179291,
-0.00950514804571867,
-0.056... | 0.025747 |
| `jobs..steps.actions/upload-artifact` | Supported | | `.artifact-subscriptions` | `jobs..steps.actions/download-artifact` | Supported | | `.docker` | `jobs..container` | Supported | | `.final-tasks` | `jobs..steps.if` | Supported | | `.requirements` | `jobs..runs-on` | Supported | | `.tasks` | `jobs..steps` | Support... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bamboo-migration.md | main | github-actions | [
-0.03558016195893288,
-0.03259965777397156,
-0.0314241424202919,
-0.0555419884622097,
0.03412036970257759,
-0.04551970586180687,
-0.04649827256798744,
-0.016783667728304863,
-0.07814182341098785,
0.06106320768594742,
-0.010412207804620266,
-0.06503994762897491,
0.0001229012996191159,
0.035... | 0.055579 |
or added under `env` for proper operation. For example, `${bamboo.jira.baseUrl}` will become {% raw %}`${{ env.jira\_baseUrl }}`{% endraw %}. ### System Variables System variables used in tasks are transformed to the equivalent bash shell variable and are assumed to be available. For example, `${system.}` will be trans... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bamboo-migration.md | main | github-actions | [
-0.04946776479482651,
-0.007066990248858929,
-0.035906948149204254,
0.011716346256434917,
0.008256480097770691,
0.01529285591095686,
0.05039137974381447,
0.029924912378191948,
0.01771744154393673,
0.03270770609378815,
0.02267608605325222,
-0.027189867570996284,
-0.008031903766095638,
0.034... | 0.045463 |
## About migrating from CircleCI with GitHub Actions Importer The instructions below will guide you through configuring your environment to use {% data variables.product.prodname\_actions\_importer %} to migrate CircleCI pipelines to {% data variables.product.prodname\_actions %}. ### Prerequisites \* A CircleCI accoun... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/circleci-migration.md | main | github-actions | [
-0.0482788048684597,
-0.07795077562332153,
-0.10840266197919846,
-0.02970360592007637,
0.04273489862680435,
-0.02531970664858818,
0.06064566224813461,
0.06739794462919235,
-0.0740465298295021,
0.009909386746585369,
0.03586515039205551,
-0.06326600164175034,
0.05578453093767166,
-0.00718016... | 0.100317 |
update ``` The output of the command should be similar to below: ```shell Updating ghcr.io/actions-importer/cli:latest... ghcr.io/actions-importer/cli:latest up-to-date ``` ## Perform an audit of CircleCI You can use the `audit` command to get a high-level view of all projects in a CircleCI organization. The `audit` co... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/circleci-migration.md | main | github-actions | [
-0.050664760172367096,
-0.049110621213912964,
-0.06880001723766327,
-0.03217432647943497,
0.07614389806985855,
-0.08836449682712555,
0.023182809352874756,
0.011538314633071423,
-0.04094010964035988,
0.017802419140934944,
0.055602334439754486,
-0.0745437890291214,
0.015276962891221046,
-0.0... | 0.105943 |
use the `migrate` command to convert a CircleCI pipeline and open a pull request with the equivalent {% data variables.product.prodname\_actions %} workflow. ### Running the migrate command To migrate a CircleCI pipeline to {% data variables.product.prodname\_actions %}, run the following command in your terminal, repl... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/circleci-migration.md | main | github-actions | [
-0.04313208907842636,
-0.026482777670025826,
-0.09136737883090973,
-0.04467024654150009,
0.042110491544008255,
-0.05359519273042679,
0.0032895493786782026,
0.051464520394802094,
-0.04012423753738403,
0.013461533933877945,
0.01064030360430479,
-0.07468598335981369,
0.035356856882572174,
-0.... | 0.066919 |
an audit. ```bash gh actions-importer audit circle-ci --output-dir ./output/ --config-file-path ./path/to/circle-ci/config.yml ``` To audit a CircleCI instance using a config file, the config file must be in the following format, and each `repository\_slug` must be unique: ```yaml source\_files: - repository\_slug: cir... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/circleci-migration.md | main | github-actions | [
-0.007200437132269144,
-0.0018276296323165298,
-0.08515077084302902,
-0.005831454414874315,
0.09946852922439575,
-0.08416374772787094,
0.06506582349538803,
-0.0010555069893598557,
0.003772967029362917,
-0.010803012177348137,
0.0628141313791275,
-0.05707192420959473,
0.044533852487802505,
-... | 0.065465 |
applicable | Unsupported | For more information about supported CircleCI concept and orb mappings, see the [`github/gh-actions-importer` repository](https://github.com/github/gh-actions-importer/blob/main/docs/circle\_ci/index.md). ### Environment variable mapping {% data variables.product.prodname\_actions\_importer %... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/circleci-migration.md | main | github-actions | [
-0.036468807607889175,
-0.028118867427110672,
-0.10825289785861969,
-0.04953252524137497,
0.013246020302176476,
-0.03547519072890282,
0.018778212368488312,
0.04381166398525238,
-0.06636350601911545,
-0.00137170625384897,
0.11818147450685501,
-0.06709467619657516,
0.05986206233501434,
-0.01... | 0.067738 |
## About migrating from Jenkins with GitHub Actions Importer The instructions below will guide you through configuring your environment to use {% data variables.product.prodname\_actions\_importer %} to migrate Jenkins pipelines to {% data variables.product.prodname\_actions %}. ### Prerequisites \* A Jenkins account o... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/jenkins-migration.md | main | github-actions | [
-0.048465415835380554,
-0.10806715488433838,
-0.050674568861722946,
-0.005288234446197748,
0.016582602635025978,
0.017206914722919464,
-0.004843398462980986,
0.06362118571996689,
-0.0906275138258934,
0.009377710521221161,
0.009298530407249928,
-0.05955345183610916,
0.04659174010157585,
0.0... | 0.034847 |
view of all pipelines in a Jenkins server. The `audit` command performs the following steps: 1. Fetches all of the projects defined in a Jenkins server. 1. Converts each pipeline to its equivalent {% data variables.product.prodname\_actions %} workflow. 1. Generates a report that summarizes how complete and complex of ... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/jenkins-migration.md | main | github-actions | [
-0.04821551963686943,
-0.04475078731775284,
-0.02660643309354782,
0.012666556052863598,
0.03728046640753746,
-0.04320757836103439,
-0.030891530215740204,
0.02896454557776451,
-0.004934772849082947,
0.008033407852053642,
-0.05295638367533684,
-0.05597594007849693,
-0.0069908336736261845,
-0... | 0.040883 |
equivalent {% data variables.product.prodname\_actions %} workflow. ### Running the dry-run command You can use the `dry-run` command to convert a Jenkins pipeline to an equivalent {% data variables.product.prodname\_actions %} workflow. A dry-run creates the output files in a specified directory, but does not open a p... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/jenkins-migration.md | main | github-actions | [
-0.06978604942560196,
-0.03338214382529259,
-0.033055443316698074,
-0.01936492882668972,
-0.0027994769625365734,
-0.007718420587480068,
0.010413646697998047,
0.04226686432957649,
-0.056065090000629425,
0.0014474475756287575,
-0.00486746896058321,
-0.022131983190774918,
0.031271882355213165,
... | 0.01275 |
files when running the `forecast` subcommand, you can use pattern matching in the file path value. For example, `gh forecast --source-file-path ./tmp/previous\_forecast/jobs/\*.json` supplies {% data variables.product.prodname\_actions\_importer %} with any source files that match the `./tmp/previous\_forecast/jobs/\*.... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/jenkins-migration.md | main | github-actions | [
-0.09849070012569427,
0.02616492286324501,
0.009161978028714657,
0.021980106830596924,
0.026398682966828346,
-0.01745586469769478,
-0.05189454182982445,
0.06007085740566254,
-0.031229199841618538,
-0.026736915111541748,
-0.054306864738464355,
-0.01961154118180275,
-0.006881598848849535,
0.... | 0.014039 |
| `{% raw %}${{ github.server\_url }}{% endraw %}` | | `${JOB\_NAME}` | `{% raw %}${{ github.workflow }}{% endraw %}` | | `${WORKSPACE}` | `{% raw %}${{ github.workspace }}{% endraw %}` | ## Legal notice {% data reusables.actions.actions-importer-legal-notice %} | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/jenkins-migration.md | main | github-actions | [
-0.020208988338708878,
-0.009307843632996082,
-0.05912598595023155,
0.06309565901756287,
0.09111691266298294,
-0.007310799788683653,
0.007621826604008675,
-0.008335663937032223,
0.020603472366929054,
0.0073881568387150764,
0.021125514060258865,
-0.008750871755182743,
0.011925091966986656,
... | 0.033696 |
## About migrating from GitLab with GitHub Actions Importer The instructions below will guide you through configuring your environment to use {% data variables.product.prodname\_actions\_importer %} to migrate GitLab pipelines to {% data variables.product.prodname\_actions %}. ### Prerequisites \* A GitLab account or o... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration.md | main | github-actions | [
-0.0730733722448349,
-0.09653422236442566,
-0.06212099269032478,
-0.0046158889308571815,
-0.018996402621269226,
-0.026101714000105858,
0.06911773979663849,
0.03703829646110535,
-0.07686115801334381,
0.008001542650163174,
0.016316663473844528,
-0.02837289683520794,
0.0821869969367981,
0.016... | -0.027602 |
The output of the command should be similar to below: ```shell Updating ghcr.io/actions-importer/cli:latest... ghcr.io/actions-importer/cli:latest up-to-date ``` ## Perform an audit of GitLab You can use the `audit` command to get a high-level view of all pipelines in a GitLab server. The `audit` command performs the f... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration.md | main | github-actions | [
-0.09220439195632935,
-0.04641474783420563,
-0.036156848073005676,
-0.022991079837083817,
0.015466410666704178,
-0.1042678952217102,
0.035295601934194565,
0.03050246462225914,
-0.04147273302078247,
0.007739929482340813,
0.04120631888508797,
-0.038512133061885834,
0.04214616119861603,
-0.01... | 0.041525 |
You can use the `dry-run` command to convert a GitLab pipeline to an equivalent {% data variables.product.prodname\_actions %} workflow. A dry-run creates the output files in a specified directory, but does not open a pull request to migrate the pipeline. To perform a dry run of migrating your GitLab pipelines to {% da... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration.md | main | github-actions | [
-0.05914764106273651,
-0.0656064823269844,
-0.02422233857214451,
0.006651461590081453,
-0.029680699110031128,
-0.07676892727613449,
0.004205958917737007,
0.021786345168948174,
-0.04232873022556305,
0.004644923377782106,
0.015591168776154518,
-0.036417294293642044,
0.07041040062904358,
0.00... | -0.04735 |
my-gitlab-namespace --project my-gitlab-project --source-file-path ./tmp/previous\_forecast/jobs/\*.json ``` #### `--config-file-path` You can use the `--config-file-path` argument with the `audit`, `dry-run`, and `migrate` subcommands. By default, {% data variables.product.prodname\_actions\_importer %} fetches pipeli... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration.md | main | github-actions | [
-0.0810624361038208,
-0.02406620979309082,
-0.014688528142869473,
0.029763536527752876,
0.021465366706252098,
-0.03627012297511101,
0.021667107939720154,
0.020535457879304886,
-0.008593558333814144,
-0.013358771800994873,
-0.029058320447802544,
-0.03713315352797508,
0.029404759407043457,
0... | -0.026786 |
Run pipelines for new commits | `on.push` | Supported | | Run pipelines manually | `on.workflow\_dispatch` | Supported | | `environment` | `jobs..environment` | Partially supported | | `include` | Files referenced in an `include` statement are merged into a single job graph before being transformed. | Partially support... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration.md | main | github-actions | [
-0.09377919882535934,
-0.05683644115924835,
-0.01118533220142126,
-0.037711258977651596,
-0.0028262226842343807,
-0.07102400809526443,
-0.048136983066797256,
-0.01421948429197073,
-0.0871889591217041,
-0.014722676016390324,
0.04798288643360138,
-0.00648797582834959,
0.04635356366634369,
0.... | -0.016382 |
%} | | `GITLAB\_USER\_EMAIL` | {% raw %}`${{ github.actor }}`{% endraw %} | | `GITLAB\_USER\_ID` | {% raw %}`${{ github.actor }}`{% endraw %} | | `GITLAB\_USER\_LOGIN` | {% raw %}`${{ github.actor }}`{% endraw %} | | `GITLAB\_USER\_NAME` | {% raw %}`${{ github.actor }}`{% endraw %} | | `TRIGGER\_PAYLOAD` | {% raw %}`${... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration.md | main | github-actions | [
-0.018324071541428566,
-0.011056187562644482,
-0.023975396528840065,
0.023071613162755966,
-0.0031307796016335487,
-0.02356429025530815,
0.0870162844657898,
0.02303503453731537,
0.01339193619787693,
-0.003761294297873974,
0.02711986005306244,
-0.08314646035432816,
0.06968972831964493,
0.01... | 0.072806 |
## About migrating from Azure DevOps with GitHub Actions Importer The instructions below will guide you through configuring your environment to use {% data variables.product.prodname\_actions\_importer %} to migrate Azure DevOps pipelines to {% data variables.product.prodname\_actions %}. ### Prerequisites \* An Azure ... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
-0.012763656675815582,
-0.10117492079734802,
-0.046718381345272064,
0.0032595705706626177,
0.018939044326543808,
0.042251862585544586,
0.03776778653264046,
0.02925090678036213,
-0.06000863015651703,
0.07382185757160187,
0.022194599732756615,
-0.04729573428630829,
0.02601681277155876,
0.035... | -0.013701 |
data variables.product.pat\_generic %} that you created earlier, and press `Enter`. \* For "Base url of the Azure DevOps instance", press `Enter` to accept the default value (`https://dev.azure.com`). \* For "Azure DevOps organization name", enter the name for your Azure DevOps organization, and press `Enter`. \* For "... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
0.017543386667966843,
-0.08108576387166977,
-0.03466131165623665,
0.00872160866856575,
0.0035188731271773577,
-0.028971275314688683,
0.03423736244440079,
-0.018500087782740593,
0.03946099057793617,
0.09419827163219452,
0.07679548114538193,
-0.058729078620672226,
0.033635396510362625,
0.020... | -0.019194 |
of jobs running at any given time. This metric can be used to define the number of runners you should configure. Additionally, these metrics are defined for each queue of runners in Azure DevOps. This is especially useful if there is a mix of hosted or self-hosted runners, or high or low spec machines, so you can see m... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
-0.030947428196668625,
-0.09136461466550827,
-0.07652366161346436,
0.016669340431690216,
-0.010566355660557747,
0.008855611085891724,
-0.005976542364805937,
-0.00301799806766212,
-0.003628247883170843,
0.04766925424337387,
-0.02137640304863453,
-0.0320875346660614,
-0.005015285219997168,
-... | 0.045008 |
using {% data variables.product.prodname\_actions\_importer %} to migrate from Azure DevOps. ### Configuration environment variables {% data reusables.actions.gai-config-environment-variables %} {% data variables.product.prodname\_actions\_importer %} uses the following environment variables to connect to your Azure De... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
-0.04033124819397926,
-0.06910073012113571,
-0.061624735593795776,
0.004285585600882769,
0.011244826950132847,
0.004943352658301592,
0.061382826417684555,
0.00845962855964899,
0.0033298467751592398,
0.06021912768483162,
-0.007690273690968752,
-0.05822150036692619,
0.04978436976671219,
0.00... | 0.055318 |
of all the reusable workflows and composite actions that were converted by {% data variables.product.prodname\_actions\_importer %}. For example, the `config.yml` file may have the following contents: ```yaml reusable\_workflows: - name: my-reusable-workflow.yml target\_url: https://github.com/octo-org/octo-repo ref: m... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
-0.037258587777614594,
-0.09944117814302444,
-0.06336814910173416,
-0.00291687180288136,
0.03131502866744995,
0.03809555619955063,
0.01597839966416359,
0.031961772590875626,
-0.04965938255190849,
-0.010543071664869785,
0.026015223935246468,
-0.006715365685522556,
0.008143110200762749,
-0.0... | 0.064045 |
raw %}`${{ github.run\_id }}`{% endraw %} | | {% raw %}`$(Build.BuildNumber)`{% endraw %} | {% raw %}`${{ github.run\_number }}`{% endraw %} | | {% raw %}`$(Build.DefinitionId)`{% endraw %} | {% raw %}`${{ github.workflow }}`{% endraw %} | | {% raw %}`$(Build.DefinitionName)`{% endraw %} | {% raw %}`${{ github.workflow... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
-0.017373304814100266,
0.014721273444592953,
-0.044659990817308426,
0.06065523996949196,
0.041420888155698776,
-0.00023363821674138308,
-0.006515664514154196,
0.026076730340719223,
0.0353204719722271,
-0.033168986439704895,
-0.03711923956871033,
-0.08259201049804688,
0.03496408462524414,
-... | 0.019141 |
%}`$(System.PullRequest.TargetBranch)`{% endraw %} | {% raw %}`${{ github.event.base.ref }}`{% endraw %} | | {% raw %}`$(System.PullRequest.TargetBranchName)`{% endraw %} | {% raw %}`${{ github.event.base.ref }}`{% endraw %} | | {% raw %}`$(System.StageAttempt)`{% endraw %} | {% raw %}`${{ github.run\_number }}`{% endr... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
0.0016689430922269821,
0.005129607859998941,
-0.05170737951993942,
0.04695792496204376,
0.018485412001609802,
0.01095445267856121,
-0.021026579663157463,
0.020191319286823273,
0.06561721116304398,
0.023044811561703682,
-0.011335168033838272,
-0.07194270938634872,
0.019170133396983147,
0.00... | 0.009096 |
name: template type: string default: simple\_step.yml steps: - template: "./templates/{% raw %}${{ parameters.template }}{% endraw %}" ``` ##### Iterative file path name example ```yaml parameters: - name: steps type: object default: - build\_step - release\_step steps: - {% raw %}${{ each step in parameters.steps }}{%... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration.md | main | github-actions | [
-0.02234180085361004,
0.035406459122896194,
-0.05143196880817413,
0.014485525898635387,
-0.028848741203546524,
0.0705399438738823,
0.018650636076927185,
0.06169977784156799,
-0.03704855591058731,
0.06540431082248688,
0.017893586307764053,
-0.03346254676580429,
-0.02217792719602585,
-0.0107... | -0.005382 |
## About migrating from Travis CI with GitHub Actions Importer The instructions below will guide you through configuring your environment to use {% data variables.product.prodname\_actions\_importer %} to migrate Travis CI pipelines to {% data variables.product.prodname\_actions %}. ### Prerequisites \* A Travis CI acc... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/travis-ci-migration.md | main | github-actions | [
-0.018586138263344765,
-0.10424748063087463,
-0.07095485925674438,
-0.01024583913385868,
-0.00967919360846281,
0.00935794971883297,
0.011038473807275295,
0.022149648517370224,
-0.08423995971679688,
0.035432200878858566,
0.057622093707323074,
-0.0687076523900032,
0.05915693938732147,
-0.013... | 0.041094 |
CI instance: https://travis-ci.com ✔ Travis CI organization name: actions-importer-labs Environment variables successfully updated. ``` 1. In your terminal, run the {% data variables.product.prodname\_actions\_importer %} `update` CLI command to connect to {% data variables.product.prodname\_registry %} {% data variabl... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/travis-ci-migration.md | main | github-actions | [
0.01399674266576767,
-0.049441009759902954,
-0.05451701208949089,
-0.03932330012321472,
0.013918634504079819,
-0.06537231802940369,
-0.024017294868826866,
0.028318477794528008,
-0.03585771098732948,
0.043286025524139404,
0.09437459707260132,
-0.08816195279359818,
0.04555036127567291,
-0.01... | 0.040451 |
data variables.product.prodname\_actions %}, run the following command in your terminal, replacing `my-travis-ci-repository` with the name of your Travis CI repository. ```shell gh actions-importer dry-run travis-ci --travis-ci-repository my-travis-ci-repository --output-dir tmp/dry-run ``` You can view the logs of the... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/travis-ci-migration.md | main | github-actions | [
-0.029862213879823685,
-0.05753019079566002,
-0.07207494229078293,
-0.013481751084327698,
0.026053303852677345,
-0.03427129238843918,
0.017568204551935196,
0.031180324032902718,
-0.05694088339805603,
0.03158707171678543,
0.0331866554915905,
-0.04300463944673538,
0.07232962548732758,
-0.040... | 0.044746 |
the specified YAML configuration file to perform an audit. ```shell gh actions-importer audit travis-ci --output-dir ./path/to/output/ --config-file-path ./path/to/travis-ci/config.yml ``` To audit a Travis CI instance using a configuration file, the file must be in the following format and each `repository\_slug` valu... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/travis-ci-migration.md | main | github-actions | [
0.030914833769202232,
-0.02483644336462021,
-0.044379137456417084,
-0.004062628373503685,
0.06873127818107605,
-0.03877091780304909,
0.04386303573846817,
-0.012694070115685463,
0.012481492944061756,
0.014564632438123226,
0.09321313351392746,
-0.05381523445248604,
0.05034536123275757,
-0.03... | 0.028796 |
endraw %} | | {% raw %}`$TRAVIS\_BUILD\_ID`{% endraw %} | {% raw %}`${{ github.run\_number }}`{% endraw %} | | {% raw %}`$TRAVIS\_BUILD\_NUMBER`{% endraw %} | {% raw %}`${{ github.run\_id }}`{% endraw %} | | {% raw %}`$TRAVIS\_COMMIT`{% endraw %} | {% raw %}`${{ github.sha }}`{% endraw %} | | {% raw %}`$TRAVIS\_EVENT\_... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/travis-ci-migration.md | main | github-actions | [
0.043417274951934814,
0.013588611967861652,
-0.03127172589302063,
0.03869623690843582,
0.04715042933821678,
0.011999140493571758,
0.005979463923722506,
-0.0001754111290210858,
0.036910708993673325,
0.027183853089809418,
0.019365649670362473,
-0.07527828961610794,
0.009599192999303341,
-0.0... | 0.045963 |
## About migrating from Bitbucket Pipelines with GitHub Actions Importer The instructions below will guide you through configuring your environment to use {% data variables.product.prodname\_actions\_importer %} to migrate Bitbucket Pipelines to {% data variables.product.prodname\_actions %}. ### Prerequisites {% data ... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bitbucket-pipelines-migration.md | main | github-actions | [
-0.034845903515815735,
-0.03983362764120102,
-0.036232054233551025,
0.01462503056973219,
0.05432087928056717,
0.016780536621809006,
-0.005270021501928568,
0.09485091269016266,
-0.0615166574716568,
0.03873110190033913,
0.05040643364191055,
-0.06727073341608047,
0.05193023383617401,
0.008988... | -0.041765 |
GitHub instance: https://github.com ✔ {% data variables.product.pat\_generic\_caps %} for Bitbucket: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ✔ Base url of the Bitbucket instance: https://bitbucket.example.com Environment variables successfully updated. ``` 1. In your terminal, run the {% data variables.product.prodnam... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bitbucket-pipelines-migration.md | main | github-actions | [
-0.026634961366653442,
-0.03830016404390335,
-0.006185592617839575,
0.0014204817125573754,
0.0469231903553009,
-0.05455534905195236,
0.032845642417669296,
0.07692249864339828,
-0.034962691366672516,
0.047186899930238724,
0.06631669402122498,
-0.04027651995420456,
0.03525025025010109,
0.039... | -0.056853 |
equivalent {% data variables.product.prodname\_actions %} workflow(s). A dry-run creates the output files in a specified directory, but does not open a pull request to migrate the pipeline. ### Running the dry-run command To perform a dry run of migrating a Bitbucket pipeline to {% data variables.product.prodname\_acti... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bitbucket-pipelines-migration.md | main | github-actions | [
-0.09090173989534378,
-0.06677313894033432,
-0.05493941530585289,
0.0017962902784347534,
0.021639475598931313,
-0.03345789015293121,
0.023477597162127495,
0.04144366458058357,
-0.056647852063179016,
0.038430362939834595,
0.02378687635064125,
-0.03245779499411583,
0.02008560486137867,
-0.00... | -0.010545 |
a config file, the config file must be in the following format, and each `repository\_slug` must be unique: ```yaml source\_files: - repository\_slug: repo\_name path: path/to/one/source/file.yml - repository\_slug: another\_repo\_name path: path/to/another/source/file.yml ``` ## Supported syntax for Bitbucket Pipeline... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bitbucket-pipelines-migration.md | main | github-actions | [
-0.02444000169634819,
-0.0430033840239048,
-0.0776839330792427,
0.005293658003211021,
-0.010714729316532612,
-0.014986428432166576,
0.015581977553665638,
0.06388504803180695,
-0.0725412368774414,
0.03935914486646652,
0.032404180616140366,
-0.051894139498472214,
0.03940449655056,
-0.0348409... | -0.019496 |
| No Mapping | | `BITBUCKET\_PARALLEL\_STEP` | No Mapping | | `BITBUCKET\_PARALLEL\_STEP\_COUNT` | No Mapping | ### System Variables System variables used in tasks are transformed to the equivalent bash shell variable and are assumed to be available. For example, `${system.}` will be transformed to `$variable\_name`. W... | https://github.com/github/docs/blob/main//content/actions/tutorials/migrate-to-github-actions/automated-migrations/bitbucket-pipelines-migration.md | main | github-actions | [
-0.008739002048969269,
-0.019569700583815575,
-0.0698775053024292,
-0.0091434670612216,
-0.03038664720952511,
0.013516529463231564,
0.043376706540584564,
0.021937016397714615,
0.009058477357029915,
0.05857196822762489,
0.07073301821947098,
-0.047759413719177246,
0.07311249524354935,
-0.029... | 0.045198 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to build and test a Swift package. {% data variables.product.prodname\_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swi... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/swift.md | main | github-actions | [
-0.03177376091480255,
-0.08638579398393631,
-0.03499216213822365,
0.005474047735333443,
0.004680977668613195,
0.0015061214799061418,
0.04018021002411842,
0.05952984839677811,
-0.06045452505350113,
-0.014298352412879467,
0.042253993451595306,
-0.004608524963259697,
-0.03297386318445206,
0.0... | 0.160717 |
{% endraw %} ## Building and testing your code You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job: ```yaml copy {% data reusables.actions.actions-not-certified-by-github-comment %} steps: - uses: {% dat... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/swift.md | main | github-actions | [
-0.02058485895395279,
-0.09461311995983124,
-0.029766632243990898,
0.07165774703025818,
0.03225528076291084,
-0.042798999696969986,
0.04078449681401253,
-0.059694841504096985,
-0.08119220286607742,
0.01796075329184532,
0.07019605487585068,
-0.024120241403579712,
-0.025777988135814667,
0.06... | 0.022627 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Maven software project management tool. The workflow you create will allow you to see when commits to a pull request cause... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/java-with-maven.md | main | github-actions | [
-0.05211137607693672,
-0.021349232643842697,
-0.049878161400556564,
-0.033490974456071854,
0.014745867811143398,
-0.02258823812007904,
-0.05749520659446716,
0.0753038078546524,
-0.046358030289411545,
0.0017804648960009217,
-0.02109227515757084,
0.015287838876247406,
0.03302035480737686,
-0... | 0.130598 |
``` ## Caching dependencies You can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored in a cache. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. You can cache de... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/java-with-maven.md | main | github-actions | [
-0.024214988574385643,
-0.0027971300296485424,
-0.029932543635368347,
-0.06443370878696442,
-0.0013507429976016283,
-0.03644494712352753,
-0.03335823863744736,
-0.0469529815018177,
0.004161234945058823,
0.017335129901766777,
0.06751567125320435,
0.047569390386343,
-0.0012009580386802554,
-... | -0.002638 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to build, test, and publish a Go package. {% data variables.product.prodname\_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the dependencies for Go. For a full list of up-to-da... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/go.md | main | github-actions | [
-0.005758253391832113,
-0.016115400940179825,
-0.050556376576423645,
-0.027309225872159004,
-0.02886316180229187,
0.02872834913432598,
0.03177584335207939,
0.08039787411689758,
-0.03145679458975792,
-0.011380798183381557,
0.05536431819200516,
0.03128520026803017,
-0.003879582043737173,
-0.... | 0.15011 |
version run: go version ``` ### Using a specific Go version You can configure your job to use a specific version of Go, such as `1.20.8`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest patch release of Go 1.21: ```yaml copy - name: Setup Go 1.21.x uses: ... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/go.md | main | github-actions | [
0.018378466367721558,
-0.01543430145829916,
0.07027924805879593,
-0.056982580572366714,
-0.018305163830518723,
0.015608340501785278,
-0.023048080503940582,
-0.011377928778529167,
-0.07082431018352509,
-0.0021216655150055885,
0.06676202267408371,
0.043132975697517395,
-0.07433713972568512,
... | -0.059975 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to build, test, and publish a Python package. {% data variables.product.prodname\_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anyt... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/python.md | main | github-actions | [
-0.03258434310555458,
-0.057586420327425,
-0.05502048507332802,
0.010392268188297749,
0.013069999404251575,
-0.02625959925353527,
-0.019681202247738838,
0.10292739421129227,
-0.0759291797876358,
0.019194992259144783,
0.02302820235490799,
0.043890561908483505,
0.015139698050916195,
-0.02977... | 0.080834 |
|\*\*Tool Cache Directory\*\* |`/opt/hostedtoolcache/\*`|`/Users/runner/hostedtoolcache/\*`|`C:\hostedtoolcache\windows\\*`| |\*\*Python Tool Cache\*\*|`/opt/hostedtoolcache/Python/\*`|`/Users/runner/hostedtoolcache/Python/\*`|`C:\hostedtoolcache\windows\Python\\*`| |\*\*PyPy Tool Cache\*\*|`/opt/hostedtoolcache/PyPy/\... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/python.md | main | github-actions | [
-0.019319258630275726,
-0.007620768155902624,
-0.056501634418964386,
-0.006467964965850115,
0.0057304175570607185,
-0.09554857015609741,
-0.03568926453590393,
-0.005184998270124197,
0.012335292994976044,
0.002025724621489644,
0.004051743075251579,
-0.0182828176766634,
-0.03320414200425148,
... | -0.054372 |
not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the `setup-python` action, {% data variables.product.prodname\_dotcom %} adds a few versions from the tools cache to `PATH`.| | macOS | The macOS runners have mo... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/python.md | main | github-actions | [
-0.01868787594139576,
-0.04301166161894798,
0.01215861551463604,
-0.0028774319216609,
0.04588930308818817,
-0.10531594604253769,
-0.08001484721899033,
0.03760934993624687,
-0.0715121328830719,
-0.02139877714216709,
0.011339617893099785,
0.050913192331790924,
0.0014931210316717625,
0.015682... | 0.052279 |
{% data reusables.actions.action-setup-python %} with: python-version: '3.x' - name: Install the code linting and formatting tool Ruff run: pipx install ruff - name: Lint code with Ruff run: ruff check --output-format=github --target-version=py39 - name: Check code formatting with Ruff run: ruff format --diff --target-... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/python.md | main | github-actions | [
-0.000519930268637836,
-0.0672478973865509,
-0.0013685704907402396,
0.015143855474889278,
0.014171536080539227,
0.01360914297401905,
0.0014966449234634638,
0.0011239154264330864,
-0.07234466820955276,
-0.014671172015368938,
-0.009200909174978733,
0.005198512692004442,
0.08025260269641876,
... | -0.05569 |
uses: {% data reusables.actions.action-upload-artifact %} with: name: release-dists path: dist/ pypi-publish: runs-on: ubuntu-latest needs: - release-build permissions: # IMPORTANT: this permission is mandatory for trusted publishing id-token: write # Dedicated environments with protections for publishing are strongly ... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/python.md | main | github-actions | [
-0.0006630282150581479,
0.013804876245558262,
-0.019567646086215973,
-0.00345621258020401,
-0.0032649370841681957,
-0.05314517393708229,
-0.027927441522479057,
0.0019970154389739037,
0.008571299724280834,
0.05623244121670723,
0.08015881478786469,
-0.014477811753749847,
-0.053664036095142365,... | -0.020682 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to build, test, and publish a Rust package. {% data variables.product.prodname\_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the dependencies for Rust. For a full list of up-t... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/rust.md | main | github-actions | [
-0.06291449069976807,
-0.03283302113413811,
-0.03900637477636337,
0.028958085924386978,
0.021106218919157982,
-0.0032475346233695745,
0.0031945379450917244,
0.1068890318274498,
-0.05217845365405083,
-0.03383231163024902,
0.007359957788139582,
0.008710311725735664,
0.021642640233039856,
-0.... | 0.223129 |
matrix: BUILD\_TARGET: [release] # refers to a cargo profile outputs: release\_built: {% raw %}${{ steps.set-output.outputs.release\_built }}{% endraw %} steps: - uses: {% data reusables.actions.action-checkout %} - name: Build binaries in "{% raw %}${{ matrix.BUILD\_TARGET }}{% endraw %}" mode run: cargo build --profi... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/rust.md | main | github-actions | [
0.00048567113117314875,
0.02653801441192627,
-0.09240101277828217,
0.0937013179063797,
0.047416433691978455,
0.015788767486810684,
0.04617692157626152,
0.01571451500058174,
-0.09713882952928543,
-0.047543250024318695,
0.030682504177093506,
-0.0482313334941864,
0.0356474444270134,
0.0099777... | 0.062994 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. The workflow you create will allow you to see when commits to a pull request cause build or test fail... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/java-with-gradle.md | main | github-actions | [
-0.06526023149490356,
-0.032517991960048676,
-0.03263596445322037,
-0.05982418358325958,
0.025893449783325195,
-0.0217893049120903,
-0.027031119912862778,
0.08437049388885498,
-0.0415969118475914,
-0.011619088239967823,
-0.04493788257241249,
0.026421761140227318,
0.02175235003232956,
-0.11... | 0.126527 |
run: ./gradlew -b ci.gradle package ``` ## Caching dependencies Your build dependencies can be cached to speed up your workflow runs. After a successful run, `gradle/actions/setup-gradle` caches important parts of the Gradle user home directory. In future jobs, the cache will be restored so that build scripts won't nee... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/java-with-gradle.md | main | github-actions | [
-0.05232756584882736,
-0.03484564274549484,
0.020152632147073746,
-0.08486905694007874,
0.0100113395601511,
-0.03895324841141701,
0.0017805631505325437,
-0.0466545969247818,
0.0207662433385849,
-0.021116767078638077,
-0.030266663059592247,
0.009057432413101196,
-0.017782039940357208,
-0.04... | -0.050953 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem. ## Prerequisites We recommend that you have a basic ... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/ruby.md | main | github-actions | [
-0.0567544624209404,
-0.04782058298587799,
-0.11308884620666504,
0.016664868220686913,
0.008616429753601551,
-0.003008422441780567,
0.0066265626810491085,
0.048701994121074677,
-0.06832804530858994,
0.016740838065743446,
0.01367988158017397,
0.0805453434586525,
0.03279580548405647,
-0.0493... | 0.086384 |
``` {% endraw %} Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see [AUTOTITLE](/actions/using-workflo... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/ruby.md | main | github-actions | [
-0.040760718286037445,
-0.027674084529280663,
-0.10486391931772232,
0.015327476896345615,
0.014558909460902214,
-0.014089827425777912,
-0.02797238901257515,
-0.08985810726881027,
-0.0167083740234375,
-0.011268537491559982,
0.0164690762758255,
0.07499600201845169,
-0.005419086664915085,
-0.... | 0.031328 |
truffleruby, truffleruby-head] continue-on-error: {% raw %}${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}{% endraw %} steps: - uses: {% data reusables.actions.action-checkout %} - uses: ruby/setup-ruby@ec02537da5712d66d4d50a0f33b7eb52773b5ed1 with: ruby-version: {% raw %}${{ matrix.ruby }}{% endraw %} -... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/ruby.md | main | github-actions | [
-0.05730718746781349,
-0.045888207852840424,
-0.11783592402935028,
0.05292895436286926,
0.042157404124736786,
0.012750995345413685,
0.02444724179804325,
0.03803013265132904,
-0.1378556340932846,
0.04532865434885025,
0.0815369188785553,
0.05527086555957794,
-0.038455531001091,
0.00858629029... | -0.005377 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. The workflow you create will allow you to see when commits to a pull request cause build or test failures against your default b... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/xamarin-apps.md | main | github-actions | [
-0.04446578398346901,
-0.02390155754983425,
0.00556271243840456,
0.0006145749357528985,
0.020395176485180855,
0.008082875050604343,
0.021023117005825043,
0.06338465213775635,
-0.009872222319245338,
0.01927845925092697,
0.016003774479031563,
-0.04830407723784447,
0.014962923713028431,
-0.03... | 0.024697 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Ant build system. The workflow you create will allow you to see when commits to a pull request cause build or test failure... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/java-with-ant.md | main | github-actions | [
-0.05290338769555092,
-0.010334638878703117,
-0.0532776340842247,
-0.04963381960988045,
0.013139106333255768,
-0.011816451326012611,
-0.0385516919195652,
0.08875646442174911,
-0.0765751525759697,
-0.0024698125198483467,
-0.0474301241338253,
0.006598536390811205,
0.009078973904252052,
-0.06... | 0.172018 |
you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see [AUTOTITLE](/actions/using-workflows/storing-workflow-data-as-artifacts). Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You c... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/java-with-ant.md | main | github-actions | [
-0.015638235956430435,
-0.023061474785208702,
-0.0017000377411022782,
-0.04390246048569679,
0.029179852455854416,
-0.002851815428584814,
0.023343976587057114,
-0.033539917320013046,
0.005322637502104044,
0.03374738246202469,
0.0395025834441185,
0.03882155567407608,
-0.08408772200345993,
-0... | 0.074152 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to use PowerShell for CI. It describes how to use Pester, install dependencies, test your module, and publish to the PowerShell Gallery. {% data variables.product.prodname\_dotcom %}-hosted runners have a tools cache ... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/powershell.md | main | github-actions | [
-0.004301501903682947,
-0.040767136961221695,
-0.1138700470328331,
0.036587346345186234,
0.036267396062612534,
0.044875264167785645,
0.0012412508949637413,
0.06475690007209778,
-0.0648564025759697,
0.06893190741539001,
0.030830027535557747,
0.009343073703348637,
0.03617754578590393,
-0.047... | 0.144554 |
jobs: install-dependencies: name: Install dependencies runs-on: ubuntu-latest steps: - uses: {% data reusables.actions.action-checkout %} - name: Install from PSGallery shell: pwsh run: | Set-PSRepository PSGallery -InstallationPolicy Trusted Install-Module SqlServer, PSScriptAnalyzer ``` > [!NOTE] > By default, no rep... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/powershell.md | main | github-actions | [
-0.020599104464054108,
-0.09631578624248505,
-0.06976723670959473,
0.017150728031992912,
0.030527843162417412,
0.04261361435055733,
0.04590383544564247,
-0.08691379427909851,
-0.03232794627547264,
0.006564883980900049,
0.00011427738354541361,
0.07349227368831635,
-0.010951130650937557,
0.0... | -0.006701 |
secrets.NUGET\_KEY }}{% endraw %} shell: pwsh run: | ./build.ps1 -Path /tmp/samplemodule Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET\_KEY -Verbose ``` | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/powershell.md | main | github-actions | [
0.0025894104037433863,
0.017836524173617363,
-0.11890915781259537,
0.047868866473436356,
0.042450904846191406,
-0.01289481669664383,
0.039232298731803894,
0.04463452845811844,
-0.012382838875055313,
0.053630415350198746,
-0.007225584704428911,
-0.024788107722997665,
0.02931625209748745,
-0... | 0.013217 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package. ## Prerequisites We recommend that you have a basic un... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/nodejs.md | main | github-actions | [
-0.06299108266830444,
-0.04263872280716896,
-0.05020804703235626,
0.021210893988609314,
0.043147772550582886,
-0.013511469587683678,
-0.03811684250831604,
0.036152031272649765,
-0.02259952574968338,
0.01885322295129299,
-0.02449219860136509,
0.08010263741016388,
0.017599204555153847,
-0.05... | 0.126783 |
about matrix strategies and contexts, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob\_idstrategymatrix) and [AUTOTITLE](/actions/learn-github-actions/contexts). ```yaml copy strategy: matrix: node-version: ['18.x', '20.x'] steps: - uses: {% data reusables.actions.action-checkout %} ... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/nodejs.md | main | github-actions | [
-0.05538445711135864,
0.0015698180068284273,
-0.07437264174222946,
0.001357327331788838,
0.030440600588917732,
0.017554061487317085,
-0.02542070858180523,
-0.08439440280199051,
0.007539229467511177,
0.018282722681760788,
0.02033674344420433,
0.042097579687833786,
-0.028361836448311806,
0.0... | 0.057048 |
sets the Node.js version, and the `registry-url` parameter sets the default registry. If your package registry uses scopes, you must use the `scope` parameter. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope). ```yaml copy steps: - uses: {% data reusables.actions.action-checkout %} - name: Use... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/nodejs.md | main | github-actions | [
-0.013186978176236153,
-0.0008525584125891328,
-0.024152686819434166,
0.04993501305580139,
0.019818976521492004,
0.019038701429963112,
-0.0044670673087239265,
0.018712414428591728,
-0.01494375430047512,
0.0820540264248848,
-0.01906534656882286,
0.03664616495370865,
-0.059146035462617874,
0... | 0.048308 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you how to build, test, and publish a .NET package. {% data variables.product.prodname\_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date s... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/net.md | main | github-actions | [
-0.035498227924108505,
-0.06351765990257263,
-0.08775554597377777,
0.015379846096038818,
0.021396413445472717,
0.005521189421415329,
0.00010310970537830144,
0.10211788862943649,
-0.051135510206222534,
0.05637724697589874,
0.008121308870613575,
0.010647544637322426,
0.03474171459674835,
-0.... | 0.183942 |
6.x uses: {% data reusables.actions.action-setup-dotnet %} with: # Semantic version range syntax or exact version of a dotnet version dotnet-version: '6.x' ``` ## Installing dependencies {% data variables.product.prodname\_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to ... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/net.md | main | github-actions | [
-0.04013412445783615,
-0.09333328157663345,
-0.0038450309075415134,
-0.021453697234392166,
0.07057005167007446,
-0.003924795426428318,
0.033403314650058746,
-0.026834873482584953,
-0.04665333777666092,
0.058810845017433167,
0.011222926899790764,
0.03834932669997215,
-0.0581638440489769,
-0... | 0.146115 |
binary. The following example creates and publishes a package to {% data variables.product.prodname\_registry %} using `dotnet core cli`. ```yaml name: Upload dotnet package on: release: types: [created] jobs: deploy: runs-on: ubuntu-latest permissions: packages: write contents: read steps: - uses: {% data reusables.ac... | https://github.com/github/docs/blob/main//content/actions/tutorials/build-and-test-code/net.md | main | github-actions | [
-0.06896136701107025,
-0.04354992136359215,
-0.043966807425022125,
-0.04387655854225159,
0.08609753847122192,
-0.0488361120223999,
0.07584818452596664,
0.017672918736934662,
-0.03539946302771568,
0.07190857082605362,
0.009899511933326721,
0.02881723828613758,
0.02483045496046543,
0.0299595... | 0.111614 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This tutorial demonstrates how to use the {% data variables.product.prodname\_cli %} in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can ... | https://github.com/github/docs/blob/main//content/actions/tutorials/manage-your-work/add-labels-to-issues.md | main | github-actions | [
-0.007084076292812824,
-0.06476477533578873,
-0.07763820141553879,
0.019648121669888496,
0.007145152892917395,
0.049394045025110245,
0.061936553567647934,
0.060826729983091354,
-0.026247546076774597,
-0.0034049921669065952,
0.010154743678867817,
0.0015734246699139476,
0.012960963882505894,
... | 0.151816 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This tutorial demonstrates how to use the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues) to comment on and close issues that have been inactive for a certain period of time. For example, you can comment if... | https://github.com/github/docs/blob/main//content/actions/tutorials/manage-your-work/close-inactive-issues.md | main | github-actions | [
-0.013948447071015835,
-0.05203384533524513,
-0.008371968753635883,
0.08219703286886215,
0.021747246384620667,
-0.02819036692380905,
0.004459889139980078,
-0.02155059017241001,
0.005607995204627514,
0.02795219235122204,
-0.017225686460733414,
0.05185621231794357,
-0.005036619957536459,
0.0... | 0.098156 |
[`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues). \* [Search GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) for examples of workflows using this action. | https://github.com/github/docs/blob/main//content/actions/tutorials/manage-your-work/close-inactive-issues.md | main | github-actions | [
-0.06115010008215904,
-0.08000867813825607,
-0.03531329706311226,
0.04713069647550583,
0.02619299106299877,
-0.03772026300430298,
-0.0008033112972043455,
-0.05160439759492874,
0.005655812099575996,
0.005775310564786196,
0.0165238119661808,
0.0865437313914299,
-0.06054171919822693,
-0.01892... | 0.187915 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This tutorial demonstrates how to use the {% data variables.product.prodname\_cli %} to comment on an issue when a specific label is applied. For example, when the `help wanted` label is added to an issue, you can add a comment to encourage c... | https://github.com/github/docs/blob/main//content/actions/tutorials/manage-your-work/add-comments-with-labels.md | main | github-actions | [
-0.033847909420728683,
-0.021052666008472443,
-0.02681679092347622,
0.010677171871066093,
0.03512239456176758,
0.05343969911336899,
0.0993986651301384,
0.03801219165325165,
-0.006073695607483387,
-0.03312844783067703,
-0.019371500238776207,
-0.028728360310196877,
0.044837065041065216,
-0.0... | 0.098278 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This tutorial demonstrates how to use the {% data variables.product.prodname\_cli %} to create an issue on a regular basis. For example, you can create an issue each week to use as the agenda for a team meeting. For more information about {% ... | https://github.com/github/docs/blob/main//content/actions/tutorials/manage-your-work/schedule-issue-creation.md | main | github-actions | [
-0.024044586345553398,
-0.045635003596544266,
-0.05528181418776512,
0.01501816138625145,
-0.0066705793142318726,
0.03282547742128372,
0.024314701557159424,
0.024251950904726982,
-0.014889809302985668,
-0.015814149752259254,
-0.009867655113339424,
0.006085917819291353,
0.033211901783943176,
... | 0.083103 |
{% data reusables.actions.schedule-delay %} You can view the history of your workflow runs to see this workflow run periodically. For more information, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history). ## Next steps \* To learn more about additional things you can do with ... | https://github.com/github/docs/blob/main//content/actions/tutorials/manage-your-work/schedule-issue-creation.md | main | github-actions | [
-0.03560059145092964,
-0.0202224962413311,
-0.03375140577554703,
0.019316425547003746,
0.01848732680082321,
0.03828892111778259,
0.06332197785377502,
0.01671922765672207,
-0.011967197991907597,
-0.04584655165672302,
0.024868184700608253,
0.0025943065993487835,
-0.01612982340157032,
-0.0398... | 0.02917 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you workflow examples that configure a service container using the Docker Hub `postgres` image. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test tha... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-postgresql-service-containers.md | main | github-actions | [
0.011050635948777199,
-0.02013431489467621,
-0.0711696594953537,
0.019515270367264748,
-0.03166234493255615,
0.002838586922734976,
0.023558199405670166,
0.027197223156690598,
-0.011007542721927166,
-0.008668803609907627,
-0.021154791116714478,
0.03266705572605133,
-0.0002870865282602608,
-... | 0.079085 |
# The default PostgreSQL port POSTGRES\_PORT: 5432 ``` {% data reusables.actions.postgres-environment-variables %} The hostname of the PostgreSQL service is the label you configured in your workflow, in this case, `postgres`. Because Docker containers on the same user-defined bridge network open all ports by default, y... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-postgresql-service-containers.md | main | github-actions | [
0.013694964349269867,
-0.01233002357184887,
-0.05195142701268196,
-0.004404738079756498,
-0.0644773617386818,
0.00002392634814896155,
-0.04869367554783821,
-0.013693483546376228,
-0.022938264533877373,
-0.03421447426080704,
-0.13229408860206604,
0.018222762271761894,
-0.0705890953540802,
-... | -0.0305 |
data, and then retrieves the data run: node client.js # Environment variables used by the `client.js` script to create # a new PostgreSQL table. env: # The hostname used to communicate with the PostgreSQL service container POSTGRES\_HOST: localhost # The default PostgreSQL port POSTGRES\_PORT: 5432 ``` {% data reusable... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-postgresql-service-containers.md | main | github-actions | [
0.027926422655582428,
-0.0014003579271957278,
-0.05931569263339043,
0.03483651205897331,
-0.08068657666444778,
-0.03924978896975517,
0.01684432663023472,
0.010127358138561249,
-0.0024705189280211926,
-0.015914876013994217,
-0.0937374085187912,
0.0021768200676888227,
-0.005299288779497147,
... | 0.031952 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The act... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-a-docker-container-action.md | main | github-actions | [
0.008919859305024147,
-0.008046870119869709,
-0.026959838345646858,
0.025325221940875053,
-0.016721315681934357,
-0.013228096067905426,
0.009580974467098713,
0.035630304366350174,
-0.028808027505874634,
0.02649025432765484,
-0.03155482932925224,
-0.024284496903419495,
0.03373176231980324,
... | 0.080946 |
to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see [AUTOTITLE](/actions/creating-actions/setting-exit-codes-for-actions). 1. Make your `entrypoint.sh` file executable. Git provides a way to explicitly change the permission mode of a file s... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-a-docker-container-action.md | main | github-actions | [
-0.013175779022276402,
-0.05628879368305206,
0.022870028391480446,
-0.03157161548733711,
0.02656535804271698,
-0.05762245133519173,
0.06459192931652069,
0.041945356875658035,
0.021304842084646225,
0.045465800911188126,
0.023700911551713943,
0.026665475219488144,
0.036057617515325546,
0.003... | 0.0292 |
action step id: hello uses: actions/hello-world-docker-action@v2 with: who-to-greet: 'Mona the Octocat' # Use the output from the `hello` step - name: Get the output time run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %} ``` ### Example using a private action Copy the following example workf... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-a-docker-container-action.md | main | github-actions | [
-0.014004610478878021,
0.03821010887622833,
-0.07077375054359436,
-0.0006976366275921464,
0.006847015582025051,
-0.026692993938922882,
0.029767388477921486,
0.06668630987405777,
-0.012754610739648342,
-0.004921059124171734,
0.012298368848860264,
-0.07671533524990082,
-0.025027526542544365,
... | 0.070398 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Introduction This guide shows you workflow examples that configure a service container using the Docker Hub `redis` image. The workflow runs a script to create a Redis client and populate the client with data. To test that the workflow creates and populat... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-redis-service-containers.md | main | github-actions | [
-0.00308500905521214,
-0.035686809569597244,
-0.08180756121873856,
0.015281863510608673,
0.00993257388472557,
-0.015608291141688824,
0.04722993075847626,
0.04016225039958954,
0.0007906602695584297,
-0.004358137492090464,
0.0012710638111457229,
0.026871753856539726,
0.03912978991866112,
-0.... | 0.134018 |
`redis`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default Redis port 6379. ## Running jobs directly on the runner machine When you run a job directly on the runner machine, you'll need to map the ports on the servi... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-redis-service-containers.md | main | github-actions | [
-0.01677100919187069,
-0.004027555696666241,
-0.10788421332836151,
-0.02307768538594246,
-0.0019316811813041568,
-0.05357618257403374,
-0.04325214400887489,
-0.001875598798505962,
0.003601840930059552,
-0.021714866161346436,
-0.06458812206983566,
0.0037473279517143965,
-0.02983865700662136,
... | 0.077349 |
can test your workflow using the following script, which creates a Redis client and populates the client with some placeholder data. The script then prints the values stored in the Redis client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `redis` npm module. For mo... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/create-redis-service-containers.md | main | github-actions | [
-0.0005979046691209078,
-0.0040787882171571255,
-0.07466805726289749,
0.03188700973987579,
-0.014336971566081047,
-0.061537403613328934,
0.04183519631624222,
0.014554382301867008,
0.04736774414777756,
-0.05449700355529785,
-0.08362738788127899,
-0.004268443677574396,
0.021362584084272385,
... | 0.105491 |
## Communicating with Docker service containers Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/use-docker-service-containers.md | main | github-actions | [
-0.03482798486948013,
-0.01846979930996895,
-0.028887726366519928,
-0.0015468262135982513,
-0.009818247519433498,
-0.031781282275915146,
0.07515785098075867,
0.009352123364806175,
-0.06777723878622055,
0.027567049488425255,
-0.06118885800242424,
0.017771832644939423,
0.051606904715299606,
... | 0.081425 |
need to map any required service container ports to ports on the host runner machine. You can map service containers ports to the Docker host using the `ports` keyword. For more information, see [`jobs..services`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob\_idservices). | Value of `ports` | Des... | https://github.com/github/docs/blob/main//content/actions/tutorials/use-containerized-services/use-docker-service-containers.md | main | github-actions | [
0.001731754164211452,
0.025109419599175453,
-0.09151837974786758,
-0.028605129569768906,
0.0009890544461086392,
-0.047718629240989685,
-0.013533225283026695,
0.0035902715753763914,
-0.051181819289922714,
0.04520147666335106,
-0.018787220120429993,
-0.018727637827396393,
0.023616870865225792,... | 0.032443 |
You can [contact {% data variables.contact.github\_support %}](/support/contacting-github-support) for assistance with {% data variables.product.prodname\_actions %}. ## Providing diagnostic and troubleshooting information The contents of private and internal repositories are not visible to {% data variables.contact.gi... | https://github.com/github/docs/blob/main//content/actions/how-tos/get-support.md | main | github-actions | [
-0.06158677116036415,
0.00941214058548212,
-0.015095577575266361,
0.02554035559296608,
0.07290930300951004,
-0.016882991418242455,
0.07206854224205017,
0.06149518862366676,
-0.04028267785906792,
-0.02953028865158558,
0.022466301918029785,
-0.012103036046028137,
0.02013368532061577,
0.01800... | 0.021394 |
debugging artifacts for a {% data variables.code-scanning.codeql\_workflow %}, see [AUTOTITLE](/code-security/code-scanning/troubleshooting-code-scanning/logs-not-detailed-enough#creating-codeql-debugging-artifacts). To provide the debugging artifacts to {% data variables.contact.github\_support %}, please download the... | https://github.com/github/docs/blob/main//content/actions/how-tos/get-support.md | main | github-actions | [
-0.027637317776679993,
0.00909564271569252,
-0.05772622302174568,
0.0013386901700869203,
0.03292696177959442,
-0.05083411931991577,
0.045605242252349854,
0.026944298297166824,
-0.07252427190542221,
0.038668494671583176,
-0.007231393828988075,
-0.007589820306748152,
0.04354001209139824,
-0.... | 0.005922 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Initial troubleshooting suggestions There are several ways you can troubleshoot failed workflow runs. {% ifversion copilot %} >[!NOTE] If you are on a {% data variables.copilot.copilot\_free %} subscription, this will count towards your monthly chat messa... | https://github.com/github/docs/blob/main//content/actions/how-tos/troubleshoot-workflows.md | main | github-actions | [
-0.001493757008574903,
-0.04364647716283798,
-0.005630312021821737,
0.05260753259062767,
-0.02757495827972889,
0.009905300103127956,
0.06345636397600174,
0.021204287186264992,
0.01486414484679699,
-0.01176378969103098,
0.016159234568476677,
-0.011877348646521568,
-0.01528480090200901,
-0.0... | 0.100474 |
the workflow. You can use special characters with filters. For more information, see [AUTOTITLE](/actions/writing-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet). For path filtering, evaluating diffs is limited to the first 300 files. If there are files changed that are not matched in the first... | https://github.com/github/docs/blob/main//content/actions/how-tos/troubleshoot-workflows.md | main | github-actions | [
-0.06357724219560623,
-0.019758783280849457,
0.005229291971772909,
-0.019215628504753113,
0.08115476369857788,
-0.07837152481079102,
0.019637640565633774,
-0.04372464865446091,
0.07994961738586426,
-0.037434328347444534,
0.015092555433511734,
0.012856182642281055,
-0.0008924836874939501,
-... | 0.078716 |
### Subnets It is possible to encounter issues with subnets in use or overlaps with an existing network, such as within virtual cloud provider or Docker networks. In such cases, we recommend you review your network topology and subnets in use. ### Certificates Issues may occur from self-signed or custom certificate cha... | https://github.com/github/docs/blob/main//content/actions/how-tos/troubleshoot-workflows.md | main | github-actions | [
-0.0027297406923025846,
-0.008100499399006367,
0.010132921859622002,
-0.013395332731306553,
0.04674084857106209,
-0.04686054587364197,
-0.04429709538817406,
-0.07008146494626999,
0.04670526832342148,
-0.05048763379454613,
-0.014456848613917828,
0.061203733086586,
0.02294200100004673,
0.040... | 0.01484 |
## Prerequisites Before starting this guide, you should be familiar with: \* The usage and security benefits of artifact attestations. See [AUTOTITLE](/actions/concepts/security/artifact-attestations). \* Generating artifact attestations. See [AUTOTITLE](/actions/security-guides/using-artifact-attestations-to-establish... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/increase-security-rating.md | main | github-actions | [
-0.10349921137094498,
0.01812177710235119,
-0.007159702945500612,
-0.028427137061953545,
0.004390610847622156,
-0.0627610981464386,
-0.0033272847067564726,
-0.016509713605046272,
-0.056614506989717484,
-0.017575370147824287,
-0.02596331760287285,
-0.09496957063674927,
0.05236344039440155,
... | 0.112652 |
## Prerequisites Before starting this guide, you should be generating artifact attestations for your builds. See [AUTOTITLE](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds). ## Step 1: Download attestation bundle First, get the attestation bundle from the attestation API. You ca... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/verify-attestations-offline.md | main | github-actions | [
-0.06015784665942192,
-0.017479870468378067,
-0.04151548817753792,
-0.04065284878015518,
0.07189430296421051,
-0.04881318658590317,
-0.03613764047622681,
-0.06906397640705109,
-0.05243752896785736,
0.05765854939818382,
0.044109415262937546,
-0.06415653973817825,
0.036746371537446976,
-0.00... | -0.042459 |
>[!NOTE] Before proceeding, ensure you have enabled build provenance for container images, including setting the `push-to-registry` attribute in the [`attest-build-provenance` action](https://github.com/actions/attest-build-provenance) as documented in [Generating build provenance for container images](/actions/securit... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/enforce-artifact-attestations.md | main | github-actions | [
0.015258789993822575,
-0.010665320791304111,
0.016289371997117996,
-0.0038916729390621185,
0.04316934198141098,
-0.020753663033246994,
-0.01679740659892559,
0.008093315176665783,
0.0202459916472435,
0.07255949079990387,
0.032409053295850754,
-0.1037287786602974,
0.0720050036907196,
0.01266... | 0.065505 |
versions: `index.docker.io/library/busybox\*\*`. Note that any image you intend to admit \_must\_ have a matching glob pattern in the `policy.images` list. If an image does not match any pattern, it will be rejected. Additionally, if an image matches both `policy.images` and `policy.exemptImages`, it will be rejected. ... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/enforce-artifact-attestations.md | main | github-actions | [
0.06214702129364014,
0.01508563756942749,
-0.004246879369020462,
-0.0064726322889328,
0.10304826498031616,
-0.11027302592992783,
-0.006087704561650753,
-0.03607062250375748,
0.027120737358927727,
0.016325972974300385,
0.010285645723342896,
-0.06917285174131393,
0.0653357282280922,
0.024051... | 0.003899 |
## Prerequisites Before you start generating artifact attestations, you need to understand what they are and when you should use them. See [AUTOTITLE](/actions/concepts/security/artifact-attestations). ## Generating artifact attestations for your builds You can use {% data variables.product.prodname\_actions %} to gene... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/use-artifact-attestations.md | main | github-actions | [
-0.025894999504089355,
-0.0018209246918559074,
-0.04206483066082001,
-0.007933092303574085,
0.04957316443324089,
-0.059576038271188736,
0.010350411757826805,
-0.025810932740569115,
-0.03453383222222328,
0.010897987522184849,
-0.0053682150319218636,
-0.12079309672117233,
0.05095133185386658,
... | 0.042309 |
SBOM attestation for container images 1. In the workflow that builds the container image you would like to attest, add the following permissions. ```yaml permissions: id-token: write contents: read attestations: write packages: write ``` 1. After the step where the image has been built, add the following step. ```yaml ... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/use-artifact-attestations.md | main | github-actions | [
0.03527127951383591,
-0.022178983315825462,
-0.06670643389225006,
0.01157839410007,
0.07224584370851517,
-0.04811641201376915,
0.01873590052127838,
0.022598549723625183,
-0.03174835070967674,
0.014790816232562065,
0.02523939125239849,
-0.046174101531505585,
0.016490360721945763,
0.05579936... | 0.06596 |
{% data reusables.actions.lifecycle-of-attestations %} ## Finding attestations 1. Navigate to the repository where the attestation was produced. {% data reusables.repositories.actions-tab %} 1. In the left sidebar, under "Management," click \*\*{% octicon "verified" aria-hidden="true" aria-label="verified" %} Attestati... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/use-artifact-attestations/manage-attestations.md | main | github-actions | [
-0.03431747481226921,
0.03333544358611107,
-0.07075387239456177,
0.11385314911603928,
0.0482051707804203,
0.06645176559686661,
0.0404546782374382,
-0.06286662071943283,
-0.06621594727039337,
0.05264020711183548,
0.036860447376966476,
-0.03785822167992592,
0.058967918157577515,
-0.030260168... | 0.00833 |
{% data reusables.actions.enterprise-github-hosted-runners %} ## Overview OpenID Connect (OIDC) allows your {% data variables.product.prodname\_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname\_dotcom %... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-google-cloud-platform.md | main | github-actions | [
-0.10156620293855667,
-0.060180697590112686,
-0.02225450426340103,
0.009691900573670864,
0.01522638276219368,
0.013266622088849545,
0.06731943041086197,
0.014837825670838356,
-0.011618576943874359,
-0.0015679681673645973,
-0.009998918510973454,
0.023811299353837967,
0.0664314478635788,
-0.... | 0.021537 |
## Overview OpenID Connect (OIDC) allows your {% data variables.product.prodname\_actions %} workflows to authenticate with [JFrog](https://jfrog.com/) to download and publish artifacts without storing JFrog passwords, tokens, or API keys in {% data variables.product.company\_short %}. This guide gives an overview of h... | https://github.com/github/docs/blob/main//content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-jfrog.md | main | github-actions | [
-0.05568623170256615,
-0.03395767882466316,
-0.07912377268075943,
0.00629283906891942,
0.02779831364750862,
-0.013012788258492947,
0.06787832826375961,
0.05237921327352524,
0.012013065628707409,
-0.05877182260155678,
-0.019701959565281868,
-0.0007204892463050783,
0.03796392306685448,
-0.01... | 0.049213 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.