Add dogfood approach to publish update-coverage to dogfood-automerge and then to gh-pages
#237
Workflow file for this run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Pull Request Created | |
| on: | |
| pull_request: | |
| types: ["opened"] | |
| jobs: | |
| PullRequestCreated_job: | |
| name: Pull Request Created | |
| runs-on: ubuntu-latest-large | |
| permissions: | |
| id-token: write | |
| # For external PR, ticket should be created manually | |
| if: | | |
| github.event.pull_request.head.repo.full_name == github.repository | |
| steps: | |
| - id: secrets | |
| uses: SonarSource/vault-action-wrapper@v3 | |
| with: | |
| secrets: | | |
| development/github/token/{REPO_OWNER_NAME_DASH}-jira token | GITHUB_TOKEN; | |
| development/kv/data/jira user | JIRA_USER; | |
| development/kv/data/jira token | JIRA_TOKEN; | |
| - uses: sonarsource/gh-action-lt-backlog/PullRequestCreated@v2 | |
| with: | |
| github-token: ${{ fromJSON(steps.secrets.outputs.vault).GITHUB_TOKEN }} | |
| jira-user: ${{ fromJSON(steps.secrets.outputs.vault).JIRA_USER }} | |
| jira-token: ${{ fromJSON(steps.secrets.outputs.vault).JIRA_TOKEN }} |