Ability for pipelines to detect Yaml configuration file from branches other than main branch during initial setup

Currently, on a new repository, when a user adds pipelines config file (bitbucket-pipelines.yml) to another branch other than the main branch (main branch does not have a config file), a pipelines build will be triggered. However, when the user clicks the Pipelines tab on the navigation panel, the UI prompts you to create a bitbucket pipelines config file and asks you to commit in order to enable pipelines.

The reason for this is because pipelines checks on the main branch for the config file for the initial setup. However, it prompts to create a new pipelines configuration file.

Steps to Reproduce

1. Create a new repository.
2. Make a new commit of any file (master as the main branch)
3. Create a new branch (develop)
4. Enable pipelines by navigating to to Repository Settings >> Pipelines >> Settings
5. Commit a new bitbucket-pipelines.yml file and notice on the commit view you can see the build status
6. Now click on the Pipelines tab on the navigation bar and you will be prompted to create a pipelines config file as it does not exist on the main branch

Request

It would be good to add a feature to detect pipelines config from from other branches as well during initial setup rather than checking only on the main branch.