Chaining workflows does not cause the subsequently spawned workflow runs to use the same event, but rather it uses the latest head SHA based on the branch it runs on. This would cause the JS benchmarks jobs to not be able to find artifacts (if a new JS repl workflow was started before the previous one could finish) and/or assign the wrong commit SHA to the benchmark results. Since `github.event` contains information about the original workflow run that spawned the JS benchmarks jobs, we can take the commit SHA from there and use it to download the correct artifact. |
||
|---|---|---|
| .. | ||
| actions | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| dependabot.yml | ||
| FUNDING.yml | ||