Dashboard › publish › Distillation
243b8983-d67b-4ec2-adde-45ddc34765cc["lore_tm_v1_CrXX8QPXD-ZG5SOLsSffpBdVtk-886VdnpFrhXwF7hw","lore_tm_v1_7uSaA2f1A1w-Y4aXTksZ418kXfxrCOPGcPcE5JaXZkw","lore_tm_v1_WUMHmUWIvFFJsLGXa3viuEs4fS9mNVWq59SxGSGtTjQ"]
🔴 (01:11) User-provided directory listing for /home/byk/Code/getsentry/publish/.github/workflows contains exactly 6 files: auto-approve.yml, ci-poller-dispatch.yml, ci-poller.yml, cocoapods-keepalive.yml, publish.yml, and test.yml.
🔴 (01:11) User-provided GitHub Actions documentation states an issue_comment event triggers a workflow only if the workflow file exists on the default branch; the event supports multiple activity types that can be restricted with types.
🔴 (01:11) User-provided GitHub Actions documentation states pull_request_review activity types are submitted, edited, and dismissed; GITHUB_SHA is the last merge commit on the GITHUB_REF branch, and GITHUB_REF is the PR merge branch refs/pull/PULL_REQUEST_NUMBER/merge.
🔴 (01:11) User-provided GitHub Actions documentation states workflows do not run in forked repositories by default; for fork-triggered workflows, secrets other than GITHUB_TOKEN are not passed to the runner, and GITHUB_TOKEN has read-only permissions for pull requests from forks.