Indentation in XML/JSON view broken #851
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: Release Issue | |
| on: | |
| issues: | |
| types: [closed, assigned] | |
| jobs: | |
| createReleaseIssue: | |
| runs-on: ubuntu-latest | |
| name: Create new Release Issue | |
| if: | | |
| contains(github.event.issue.labels.*.name, 'release') && | |
| github.event.action == 'closed' | |
| outputs: | |
| assignee: ${{ steps.createReleaseIssue.outputs.assignee }} | |
| steps: | |
| - id: createReleaseIssue | |
| name: Create new Release Issue | |
| uses: bpmn-io/actions/release-issue@latest | |
| with: | |
| template-path: 'docs/.project/RELEASE_TEMPLATE.md' | |
| package-path: 'app/package.json' | |
| assignMilestone: | |
| needs: createReleaseIssue | |
| if: github.event.issue.milestone | |
| runs-on: ubuntu-latest | |
| name: Assign Milestone | |
| steps: | |
| - name: Get current Milestone | |
| id: getMilestone | |
| env: | |
| GH_TOKEN: ${{ github.token }} | |
| run: | | |
| # Fetch the list of milestones for the repository | |
| # Filter for milestones that start with 'M' and are open | |
| MILESTONE=$(gh api -H "Accept: application/vnd.github.v3+json" \ | |
| /repos/${{ github.repository }}/milestones \ | |
| --jq '.[] | select(.title | startswith("M")) | .number' | |
| ) | |
| echo "MILESTONE_NUMBER=$MILESTONE" >> $GITHUB_OUTPUT | |
| - name: Assign Milestone to new Issue | |
| env: | |
| GH_TOKEN: ${{ github.token }} | |
| run: | | |
| gh api \ | |
| --method PATCH \ | |
| -H "Accept: application/vnd.github+json" \ | |
| /repos/${{ github.repository }}/issues/${{ fromJson(needs.createReleaseIssue.outputs.issue).number }} \ | |
| -F "milestone=${{steps.getMilestone.outputs.MILESTONE_NUMBER}}" | |
| updateSlackRole: | |
| runs-on: ubuntu-latest | |
| if: | | |
| always() && | |
| contains(github.event.issue.labels.*.name, 'release') | |
| name: Sync Slack roles | |
| needs: createReleaseIssue | |
| steps: | |
| - name: Import Secrets | |
| id: secrets | |
| uses: hashicorp/vault-action@v3.0.0 | |
| with: | |
| url: ${{ secrets.VAULT_ADDR }} | |
| method: approle | |
| roleId: ${{ secrets.VAULT_ROLE_ID }} | |
| secretId: ${{ secrets.VAULT_SECRET_ID }} | |
| exportEnv: false | |
| secrets: | | |
| secret/data/products/desktop-modeler/ci/slack_integration RELEASE_MANAGER_GROUP_ID; | |
| secret/data/products/desktop-modeler/ci/slack_integration SLACK_BOT_TOKEN; | |
| secret/data/products/desktop-modeler/ci/slack_integration TEAM_MEMBER_IDS; | |
| - name: Update slack | |
| env: | |
| BOT_TOKEN: ${{ steps.secrets.outputs.SLACK_BOT_TOKEN }} | |
| GROUP_ID: ${{ steps.secrets.outputs.RELEASE_MANAGER_GROUP_ID }} | |
| # User ID is either the assignee from the newly created issue or the new assigned from the `assigned` trigger | |
| USER_ID: ${{ fromJSON(steps.secrets.outputs.TEAM_MEMBER_IDS)[ needs.createReleaseIssue.outputs.assignee || github.event.issue.assignee.login ] }} | |
| run: | | |
| curl --fail-with-body -X POST -H "application/x-www-form-urlencoded" -d "token=${BOT_TOKEN}&usergroup=${GROUP_ID}&users=${USER_ID}" https://slack.com/api/usergroups.users.update |