NET-589 Create rule S7131: You should not release a write lock when a read lock has been acquired and vice versa #31
Workflow file for this run
This file contains 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 Closed | |
| on: | |
| pull_request: | |
| types: [closed] | |
| jobs: | |
| PullRequestMerged_job: | |
| name: Pull Request Merged | |
| runs-on: ubuntu-latest | |
| permissions: | |
| id-token: write | |
| pull-requests: read | |
| # For external PR, ticket should be moved manually | |
| if: | | |
| github.event.pull_request.head.repo.full_name == github.repository | |
| && github.event.pull_request.merged | |
| steps: | |
| - id: secrets | |
| uses: SonarSource/vault-action-wrapper@v3 | |
| with: | |
| secrets: | | |
| development/kv/data/jira user | JIRA_USER; | |
| development/kv/data/jira token | JIRA_TOKEN; | |
| - uses: sonarsource/gh-action-lt-backlog/PullRequestClosed@v2 | |
| with: | |
| github-token: ${{secrets.GITHUB_TOKEN}} | |
| jira-user: ${{ fromJSON(steps.secrets.outputs.vault).JIRA_USER }} | |
| jira-token: ${{ fromJSON(steps.secrets.outputs.vault).JIRA_TOKEN }} |