Problem Definition

Assume a repository where Pipelines is not enabled yet. The repo has two branches, featureA and main, and a PR from featureA to main.

A user commits and pushes a bitbucket-pipelines.yml file to featureA branch.

Then, they open the page of the PR on the Bitbucket website. On the right-side panel of the PR they see the message:

It looks like you haven’t configured a build tool yet. You can use Bitbucket Pipelines to build, test and deploy your code.

Your existing plan already includes build minutes.

Set up a pipeline

If they select the link Set up a pipeline, the Pipelines page of the repo opens, along with the templates asking the user to create their first pipeline.

This can be confusing to the user, since they already committed a bitbucket-pipelines.yml file to the repo.

Suggested Solution

If a yml file exists in any branch of the repo and Pipelines is not enabled, show a different message in the PR asking the user to enable Pipelines from Repository settings.

Additionally, instead of the text Set up a pipeline, show Run pipeline. When the user gets redirected to the Pipelines page, provide the option to run the first pipeline, instead of asking the user to create their first pipeline.