Allow outside contributors to run CI with secrets when approved
Merged
PI
9mo ago+102+102+012345678901234567890123456789-26-26-01234567890123456789
PSA potential hackers: dont get excited, we don't have any real secrets in CI worth stealing, and our CI does not autodeploy anything to prod. All important secrets and CD processes are kept in our closed-source repos.
why
what changed
test plan
Summary by cubic
Add a gating workflow that blocks CI until a maintainer approves running secrets on forked PRs. CI now triggers from that gate, resolves labels and path filters under workflow_run, removes same-repo guards so integration/e2e/evals run on approved forks, and checks out the PR commit consistently across jobs.