|
| 1 | +name: Changes In High Risk Code |
| 2 | +on: |
| 3 | + pull_request: |
| 4 | + |
| 5 | +# https://docs.github.com/en/actions/using-jobs/using-concurrency#example-using-a-fallback-value |
| 6 | +concurrency: |
| 7 | + group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }} |
| 8 | + cancel-in-progress: true |
| 9 | + |
| 10 | +jobs: |
| 11 | + files-changed: |
| 12 | + name: Detect changed files |
| 13 | + runs-on: ubuntu-latest |
| 14 | + # Map a step output to a job output |
| 15 | + outputs: |
| 16 | + high_risk_code: ${{ steps.changes.outputs.high_risk_code }} |
| 17 | + high_risk_code_files: ${{ steps.changes.outputs.high_risk_code_files }} |
| 18 | + steps: |
| 19 | + - uses: actions/checkout@v4 |
| 20 | + - name: Get changed files |
| 21 | + id: changes |
| 22 | + uses: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36 # v3.0.2 |
| 23 | + with: |
| 24 | + token: ${{ github.token }} |
| 25 | + filters: .github/file-filters.yml |
| 26 | + |
| 27 | + # Enable listing of files matching each filter. |
| 28 | + # Paths to files will be available in `${FILTER_NAME}_files` output variable. |
| 29 | + list-files: csv |
| 30 | + |
| 31 | + validate-high-risk-code: |
| 32 | + if: needs.files-changed.outputs.high_risk_code == 'true' |
| 33 | + needs: files-changed |
| 34 | + runs-on: ubuntu-latest |
| 35 | + steps: |
| 36 | + - name: Comment on PR to notify of changes in high risk files |
| 37 | + uses: actions/github-script@v7 |
| 38 | + env: |
| 39 | + high_risk_code: ${{ needs.files-changed.outputs.high_risk_code_files }} |
| 40 | + with: |
| 41 | + script: | |
| 42 | + const highRiskFiles = process.env.high_risk_code; |
| 43 | + const fileList = highRiskFiles.split(',').map(file => `- [ ] ${file}`).join('\n'); |
| 44 | + |
| 45 | + // Get existing comments |
| 46 | + const comments = await github.rest.issues.listComments({ |
| 47 | + issue_number: context.issue.number, |
| 48 | + owner: context.repo.owner, |
| 49 | + repo: context.repo.repo |
| 50 | + }); |
| 51 | + |
| 52 | + // Check if we already have a high risk code comment |
| 53 | + const hasExistingComment = comments.data.some(comment => |
| 54 | + comment.body.includes('🚨 Detected changes in high risk code 🚨') |
| 55 | + ); |
| 56 | + |
| 57 | + // Only create comment if we don't already have one |
| 58 | + if (!hasExistingComment) { |
| 59 | + await github.rest.issues.createComment({ |
| 60 | + issue_number: context.issue.number, |
| 61 | + owner: context.repo.owner, |
| 62 | + repo: context.repo.repo, |
| 63 | + body: `### 🚨 Detected changes in high risk code 🚨 \n High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:\n ${fileList}` |
| 64 | + }); |
| 65 | + } |
0 commit comments