{"id":21721342,"url":"https://github.com/informaticsmatters/trigger-ci-action","last_synced_at":"2025-04-12T21:33:50.157Z","repository":{"id":65157789,"uuid":"349532866","full_name":"InformaticsMatters/trigger-ci-action","owner":"InformaticsMatters","description":"A GitHub Action to trigger CI build","archived":false,"fork":false,"pushed_at":"2024-04-22T19:57:36.000Z","size":19,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-26T15:47:59.537Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/InformaticsMatters.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2021-03-19T19:22:35.000Z","updated_at":"2023-04-25T01:27:42.000Z","dependencies_parsed_at":"2025-04-12T21:32:46.314Z","dependency_job_id":null,"html_url":"https://github.com/InformaticsMatters/trigger-ci-action","commit_stats":{"total_commits":8,"total_committers":1,"mean_commits":8.0,"dds":0.0,"last_synced_commit":"86a187932ffa16df10523eeb341cd216e349bc61"},"previous_names":[],"tags_count":2,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InformaticsMatters%2Ftrigger-ci-action","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InformaticsMatters%2Ftrigger-ci-action/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InformaticsMatters%2Ftrigger-ci-action/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InformaticsMatters%2Ftrigger-ci-action/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/InformaticsMatters","download_url":"https://codeload.github.com/InformaticsMatters/trigger-ci-action/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248636815,"owners_count":21137527,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-26T02:15:58.792Z","updated_at":"2025-04-12T21:33:50.131Z","avatar_url":"https://github.com/InformaticsMatters.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Trigger CI Action\nA container-based GitHub Action that triggers execution of a remote CI process.\nThis can be used to chain CI builds that might exist in disperate repositories.\nThe action essentially allows the build process in repository\n**\"A\"** to trigger a named CI process in repository **\"B\"**.\n\nThe Trigger CI action supports the triggering the following remotes CI\nprocesses: -\n\n-   **GitHub Workflow Dispatch** (`ci-type: github-workflow-dispatch`)\n\n## Inputs\n\n### `ci-type`\n**Optional** The type of remote CI process to trigger.\nAt the moment we support the following types: -\n\n- `github-workflow-dispatch`\n\n### `ci-owner`\n**Required** The remote repository owner, i.e. `informaticsmatters` if the\nremote CI repository is `informaticsmatters/squonk`\n\n### `ci-repository`\n**Required** The repository name, i.e. `squonk` if the\nremote CI repository is `informaticsmatters/squonk`\n\n### `ci-ref`\n**Optional** The repository reference to trigger.\nIt's the fully qualified remote reference, a branch or a tag. Default is\n`refs/heads/main`, but can be a branch, i.e. `refs/heads/dev-branch`\nor a tag, i.e. `refs/tags/2021.3`, or any valid reference.\n\nFor _new-style_ GitHub repositories the default will be sufficient to trigger\na build on the main branch (where the main branch is now called `main`).\nFor older repositories you may have to use this input and\nset it to the old main name, e.g. `refs/heads/master`\n\n### `ci-user`\n**Required** A user that can access the remote repository\n\n### `ci-user-token`\n**Required** The repository user's access token\n\n### `ci-name`\n**Required** The name of the remote CI process, for **GitHub Workflow Dispatch**\ntypes this will be the `name` assigned to the workflow you're running, which is\nthe `name` defined in the workflow file, _not_ the workflow file name.\n\n### `ci-inputs`\n**Optional** The remote repository's build inputs or arguments. If used,\nit is used to set build arguments and values in remote CI processes that\nsupport this mechanism. For **GitHub Workflow Dispatch** types\nthese will be used to set corresponding _workflow inputs_.\nThe inputs are declared here using a space-separated set of names and values, \ni.e. `target_input_1=xyx target_input_2=abc`, where `target_input_1` and\n`target_input_2` are inputs declared in the remote workflow's\n`workflow_dispatch` configuration.\n\n\u003e   Do not put spaces around the input's '='. The action expects\n    each key and value in the form \u003ckey\u003e=\u003cvalue\u003e.\n\n## Example usage\nIn this first example we trigger the default type of workflow\n(a **GitHub Workflow Dispatch** workflow) on the branch `dev-branch`\n(`refs/heads/dev-branch`) of the repository `informaticsmatters/squonk`.\nThe workflow name being executed is `build main`.\n\n\u003e   Every trigger needs a user (and user token) that can activate the remote CI\n    process, illustrated here using secrets available to the triggering\n    repository's workflow.\n\n```yaml\n- name: Trigger squonk\n  uses: informaticsmatters/trigger-ci-action@v1\n  with:\n    ci-owner: informaticsmatters\n    ci-repository: squonk\n    ci-ref: refs/heads/dev-branch\n    ci-name: build main\n    ci-user: ${{ secrets.SQUONK_USER }}\n    ci-user-token: ${{ secrets.SQUONK_USER_TOKEN }}\n```\n\nIf the remote CI process accepts inputs we can provide values for them using\nthe action's `ci-inputs` property by providing a space-separated set of\nkeys and values.\n\nHere we provide values `xyz` and `abc` for the inputs `target_input_1` and\n`target_input_2`: -\n\n```yaml\n- name: Trigger squonk with inputs\n  uses: informaticsmatters/trigger-ci-action@v1\n  with:\n    ci-owner: informaticsmatters\n    ci-repository: squonk\n    ci-name: build main\n    ci-inputs: \u003e-\n      target_input_1=xyx\n      target_input_2=abc\n    ci-user: ${{ secrets.SQUONK_USER }}\n    ci-user-token: ${{ secrets.SQUONK_USER_TOKEN }}\n```\n\n---\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Finformaticsmatters%2Ftrigger-ci-action","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Finformaticsmatters%2Ftrigger-ci-action","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Finformaticsmatters%2Ftrigger-ci-action/lists"}