feat(telemetry): capture and report native crashes via Crashpad #11371
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 Assistant" | |
| on: | |
| issue_comment: | |
| types: [created] | |
| pull_request_target: | |
| types: [opened, closed, synchronize] | |
| # Restrict default permissions to read-only at workflow level; grant only | |
| # what the job needs at job level (principle of least privilege). | |
| permissions: {} | |
| jobs: | |
| CLAAssistant: | |
| runs-on: ubuntu-latest | |
| permissions: | |
| contents: write # store CLA signatures in the repo | |
| pull-requests: write # post CLA status comments on PRs | |
| statuses: write # update commit status checks | |
| steps: | |
| - name: "CLA Assistant" | |
| if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target' | |
| uses: contributor-assistant/github-action@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1 | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| # the below token should have repo scope and must be manually added by you in the repository's secret | |
| # This token is required only if you have configured to store the signatures in a remote repository/organization | |
| # PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }} | |
| with: | |
| path-to-signatures: "signatures/version1/cla.json" | |
| path-to-document: "https://github.com/dyad-sh/dyad/blob/main/CLA.md" | |
| # branch should not be protected | |
| branch: "cla" | |
| allowlist: claude | |
| # the followings are the optional inputs - If the optional inputs are not given, then default values will be taken | |
| #remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository) | |
| #remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository) | |
| #create-file-commit-message: 'For example: Creating file for storing CLA Signatures' | |
| #signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo' | |
| #custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign' | |
| #custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA' | |
| #custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.' | |
| lock-pullrequest-aftermerge: false # don't lock comments after closing PR, we want ai code reviewers to still comment afterwards. | |
| #use-dco-flag: true - If you are using DCO instead of CLA |