Hello @T-compiler! I'm really happy to say that we finally started double-gating CI on both Azure Pipelines and GitHub Actions! :tada: :tada: :tada:
What does this mean?
This is the last step before fully migrating to GitHub Actions: bors will now require both Azure Pipelines and GitHub Actions for a PR to be tried or merged. The practical impact is that build failures will be reported faster (as GitHub Actions will fail before Azure Pipelines), while green builds will still be slow (as we need to wait for Azure Pipelines).
Why is the double-gate needed?
The double gate allows us to spot the last issues with the GitHub Actions configuration while still making sure we're not landing bad code (as Azure Pipelines is still running).
What if I notice a spurious failure?
If you notice any issue due to GitHub Actions please ping the infrastructure team.
@Pietro Albini woohoo!