├── .circleci └── config.yml ├── .eslintrc.cjs ├── .github ├── CODEOWNERS ├── ISSUE_TEMPLATE │ ├── BUG.yml │ └── FEATURE_REQUEST.yml └── PULL_REQUEST_TEMPLATE │ └── PULL_REQUEST.md ├── .gitignore ├── .husky └── pre-commit ├── .nvmrc ├── .prettierrc.json ├── CONTRIBUTING.md ├── README.md ├── __tests__ └── CircleCIPipelineTrigger.test.ts ├── action.yml ├── dist ├── index.js └── licenses.txt ├── examples ├── 01-Trigger-Workflow-On-Pull_Request │ ├── .circleci │ │ └── config.yml │ ├── .github │ │ └── workflows │ │ │ └── main.yml │ └── README.md └── 02-Trigger-Workflow-On-Release │ ├── .circleci │ └── config.yml │ ├── .github │ └── workflows │ │ └── main.yml │ └── README.md ├── jest.config.ts ├── package-lock.json ├── package.json ├── src ├── index.ts └── lib │ └── CircleCIPipelineTrigger.ts └── tsconfig.json /.circleci/config.yml: -------------------------------------------------------------------------------- 1 | version: 2.1 2 | orbs: 3 | node: circleci/node@5.1.0 4 | workflows: 5 | test: 6 | jobs: 7 | - node/test: 8 | test-results-for: jest 9 | -------------------------------------------------------------------------------- /.eslintrc.cjs: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | extends: ["eslint:recommended", "plugin:@typescript-eslint/recommended"], 3 | parser: "@typescript-eslint/parser", 4 | plugins: ["@typescript-eslint"], 5 | root: true, 6 | }; 7 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | @KyleTryon 2 | @CircleCI-Public/cpeng -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/BUG.yml: -------------------------------------------------------------------------------- 1 | name: "\U0001F41E Bug Report" 2 | description: Report any identified bugs. 3 | title: 'Bug: ' 4 | labels: [bug] 5 | # assignees: '' 6 | body: 7 | - type: checkboxes 8 | attributes: 9 | label: "Is there an existing issue for this?" 10 | description: "Please search [here](https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/issues?q=is%3Aissue) to see if an issue already exists for the bug you encountered" 11 | options: 12 | - label: "I have searched the existing issues" 13 | required: true 14 | 15 | - type: textarea 16 | validations: 17 | required: true 18 | attributes: 19 | label: "Current behavior" 20 | description: "How does the issue manifest?" 21 | 22 | - type: input 23 | validations: 24 | required: true 25 | attributes: 26 | label: "Minimum reproduction code" 27 | description: "An URL to some git repository or gist which contains the minimum needed code to reproduce the error" 28 | placeholder: "https://github.com/..." 29 | 30 | - type: textarea 31 | attributes: 32 | label: "Steps to reproduce" 33 | description: | 34 | Detail the steps to take to replicate the issue. 35 | You may leave this blank if you have covered the issue in the minimum reproduction code above. 36 | placeholder: | 37 | 1. `npm i` 38 | 2. `npm start:dev` 39 | 3. See error... 40 | 41 | - type: textarea 42 | validations: 43 | required: true 44 | attributes: 45 | label: "Expected behavior" 46 | description: "A clear and concise description of what you expected to happen (or code)" 47 | 48 | - type: markdown 49 | attributes: 50 | value: | 51 | --- 52 | 53 | - type: input 54 | attributes: 55 | label: "GitHub Action Version" 56 | description: | 57 | Which version of `trigger-circleci-pipeline` are you using? 58 | placeholder: "1.0.0" 59 | 60 | - type: textarea 61 | attributes: 62 | label: "Other" 63 | description: | 64 | Anything else relevant? 65 | **Tip:** You can attach images, recordings or log files by clicking this area to highlight it and then dragging files in. 66 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/FEATURE_REQUEST.yml: -------------------------------------------------------------------------------- 1 | name: "\U0001F4A1 Feature Request" 2 | description: Have an idea for a new feature? Begin by submitting a Feature Request 3 | title: 'Request: ' 4 | labels: [feature_request] 5 | # assignees: '' 6 | body: 7 | - type: checkboxes 8 | attributes: 9 | label: "Is there an existing issue that is already proposing this?" 10 | description: "Please search [here](https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/issues?q=is%3Aissue) to see if an issue already exists for the feature you are requesting" 11 | options: 12 | - label: "I have searched the existing issues" 13 | required: true 14 | - type: textarea 15 | id: contact 16 | attributes: 17 | label: "Is your feature request related to a problem? Please describe it" 18 | description: "A clear and concise description of what the problem is" 19 | placeholder: | 20 | I have an issue when ... 21 | validations: 22 | required: false 23 | - type: textarea 24 | validations: 25 | required: true 26 | attributes: 27 | label: "Describe the solution you'd like" 28 | description: "A clear and concise description of what you want to happen. Add any considered drawbacks" 29 | - type: textarea 30 | validations: 31 | required: true 32 | attributes: 33 | label: "Teachability, documentation, adoption, migration strategy" 34 | description: "If you can, explain how users will be able to use this and possibly write out a version the docs." 35 | - type: textarea 36 | validations: 37 | required: true 38 | attributes: 39 | label: "What is the motivation / use case for changing the behavior?" 40 | description: "Describe the motivation or the concrete use case" -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST.md: -------------------------------------------------------------------------------- 1 | ## PR Checklist 2 | Please check if your PR fulfills the following requirements: 3 | 4 | - [ ] The commit message follows our contributor [guidelines](https://github.com/CircleCI-Public/circleci-config-sdk-ts/blob/main/CONTRIBUTING.md). 5 | - [ ] Tests for the changes have been added (for bug fixes / features) 6 | - [ ] Documentation has been added or updated where needed. 7 | 8 | ## PR Type 9 | What kind of change does this PR introduce? 10 | 11 | 12 | 13 | - [ ] Bug fix 14 | - [ ] Feature 15 | - [ ] Code style update (formatting, local variables) 16 | - [ ] Refactoring (no functional changes, no api changes) 17 | - [ ] Build related changes 18 | - [ ] CI related changes 19 | - [ ] Other... Please describe: 20 | 21 | > more details 22 | 23 | ## What issues are resolved by this PR? 24 | 25 | - #[00] 26 | 27 | ## Describe the new behavior. 28 | 29 | 30 | > Description 31 | 32 | ## Does this PR introduce a breaking change? 33 | 34 | - [ ] Yes 35 | - [ ] No 36 | 37 | 38 | 39 | ## Other information 40 | 41 | 42 | > More information (optional) 43 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules/ 2 | .DS_Store 3 | .idea 4 | .vscode -------------------------------------------------------------------------------- /.husky/pre-commit: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | . "$(dirname "$0")/_/husky.sh" 3 | 4 | npm run lint && npm run format && npm run build 5 | # Stage modified files 6 | ## https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/pull/51#discussion_r1152164608 7 | # git add $(git diff --name-only) -------------------------------------------------------------------------------- /.nvmrc: -------------------------------------------------------------------------------- 1 | v16 2 | -------------------------------------------------------------------------------- /.prettierrc.json: -------------------------------------------------------------------------------- 1 | {} 2 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Thank you for considering to contribute to the CircleCI Config SDK! Before you 4 | get started, we recommend taking a look at the guidelines belowL 5 | 6 | - [Have a Question?](#question) 7 | - [Issues and Bugs](#issue) 8 | - [Feature Requests](#feature) 9 | - [Contributing](#contribute) 10 | - [Submission Guidelines](#guidelines) 11 | - [Release Process](#release) 12 | 13 | ## Have a Question? 14 | 15 | ### I have a general question about CircleCI or CircleCI's `config.yml` file. 16 | 17 | Contact CircleCI's general support by filing a ticket here: 18 | [Submit a request](https://support.circleci.com/hc/en-us/requests/new) 19 | 20 | 21 | ## Discover a Bug? 22 | 23 | Find an issue or bug? 24 | 25 | You can help us resolve the issue by 26 | [submitting an issue](https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/issues) 27 | on our GitHub repository. 28 | 29 | Up for a challenge? If you think you can fix the issue, consider sending in a 30 | [Pull Request](#pull). 31 | 32 | ## Missing Feature? 33 | 34 | Is anything missing? 35 | 36 | You can request a new feature by 37 | [submitting an issue](https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/issues) 38 | to our GitHub repository, utilizing the `Feature Request` template. 39 | 40 | If you would like to instead contribute a pull request, please follow the 41 | [Submission Guidelines](#guidelines) 42 | 43 | ## Contributing 44 | 45 | Thank you for contributing to the CircleCI Config SDK! 46 | 47 | Before submitting any new Issue or Pull Request, search our repository for any 48 | existing or previous related submissions. 49 | 50 | - [Search Pull Requests](https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/pulls?q=) 51 | - [Search Issues](https://github.com/CircleCI-Public/trigger-circleci-pipeline-action/issues?q=) 52 | 53 | ### Submission Guidelines 54 | 55 | #### Commit Conventions 56 | 57 | This project strictly adheres to the 58 | [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) 59 | specification for creating human readable commit messages with appropriate 60 | automation capabilities, such as changelog generation. 61 | 62 | ##### Commit Message Format 63 | 64 | Each commit message consists of a header, a body and a footer. The header has a 65 | special format that includes a type, a scope and a subject: 66 | 67 | ``` 68 | (optional ): 69 | 70 | 71 | 72 |