When GitLab CI YAML is invalid and user clicks "Go to the Pipeline Editor", the editor should open on the correct branch

When a pipeline is pushed with an invalid GitLab CI YAML to a branch/merge request, the user is prompted to go to the Pipeline Editor. This is helpful as it allows the developer to understand further why the pipeline is failing.

However, when the user clicks the "Go to Pipeline Editor", they are presented with the GitLab CI for the default branch. This is surprising, since the user is in the context of the failing branch, so why present them with a (presumably correct) GitLab CI configuration.

It would be a much better developer experience (imho) to take the user directly to the pipeline editor for the failing branch.

The alternative is that the engineer needs to figure out the name of the branch, the find it in the list. This is a small but developer-unfriendly extra step that seems needlessly complicated.