This is safer since we only ever added one new branch as a long-living branch while it's much more likely to accidentally push a new, large branch to the upstream remote (this repository).

We don't cancel older pipelines if new commits are pushed to branches on this repo (so that we know that merging these commits produce a green build). We previously ignored known branches but #22620 and #22618 used a different naming scheme and queued hundreds of pipeline runs. Maybe we can cancel these via API.

For future self:

• cancel jobs on a branch script: https://gist.github.com/eps1lon/9c822429bffb5db5a3f221dd00fea842
• workflows can still be considered running even if all underlying jobs are cancelled.