Not so pretty, but a better-than-nothing solution to be able to run the acceptance tests for external PRs after having manually validated them.
Usage
Do a manual sanity check on the submitted code and copy the branch's latest commit hash, go to the Actions tab -> Run acceptance tests and press the Run workflow button (note: button doesn't show yet, because this PR needs to be on main first). Paste in the commit hash you verified and enter the fork repository name, and it will run the acceptance tests including the secrets needed to run the tests.
Downsides of this approach:
No automatic reporting back to the PR
We have to keep a branch / commit open to attach all the workflow runs to, to avoid messing up our main branch commits with false alarm red Xs. I've created acceptance-tests-on-forks for this purpose.
If GitHub ever releases an Approve workflow run with secrets button for external PRs, then we can revert this PR.
Not so pretty, but a better-than-nothing solution to be able to run the acceptance tests for external PRs after having manually validated them.
Usage
Do a manual sanity check on the submitted code and copy the branch's latest commit hash, go to the
Actionstab ->Run acceptance testsand press theRun workflowbutton (note: button doesn't show yet, because this PR needs to be onmainfirst). Paste in the commit hash you verified and enter the fork repository name, and it will run the acceptance tests including the secrets needed to run the tests.Downsides of this approach:
acceptance-tests-on-forksfor this purpose.If GitHub ever releases an
Approve workflow run with secretsbutton for external PRs, then we can revert this PR.