MOLCodesignChecker: Fix the initWithSecStaticCodeRef: initializers #125
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: CLA | |
| on: | |
| issue_comment: | |
| types: [created] | |
| # pull_request_target (not pull_request) is REQUIRED: PRs from forks get a read-only | |
| # token with no access to secrets, so a plain `pull_request` run could neither read the | |
| # App key nor post the CLA comment/status — i.e. it couldn't gate external contributors, | |
| # which is the whole point. pull_request_target runs in the BASE repo's context, which has | |
| # both. It is SAFE here because this workflow never checks out or runs the PR's code | |
| # (no actions/checkout of the PR head) — it only reads PR metadata via the API, so the | |
| # secret-bearing context is never exposed to attacker-controlled code. | |
| pull_request_target: | |
| types: [opened, synchronize, reopened] | |
| jobs: | |
| cla: | |
| # issue_comment also fires for comments on ordinary issues; skip those so the runner | |
| # only starts for PR comments and PR events. | |
| if: github.event_name != 'issue_comment' || github.event.issue.pull_request | |
| runs-on: ubuntu-latest | |
| permissions: | |
| pull-requests: write # post/update the CLA comment | |
| statuses: write # set the CLA status check | |
| steps: | |
| - uses: northpolesec/cla/.github/actions/cla@b1b3a870365a1622d80914793e41f098734f8883 | |
| with: | |
| app-id: ${{ secrets.CLA_APP_ID }} | |
| private-key: ${{ secrets.CLA_APP_KEY }} |