nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I remove this ugly pipeline thing I just created

Alan Holden

So I thought I had followed the Getting Started instructions to create my first pipeline.

But now the UI for this creation is filled with red error icons, and messgaes read as though I had intended my first one to affect our master repo. Definitely not my intention.

So, how do I simply remove this malignancy and go back to the days where I never "Got Started"? I just want to begin again, trial and error, without consequences like this.

TIA, AL

HOW DO I DELETE THIS CRUD?

Accepted answers

Ajay _view26_

Hi @Alan Holden

The red errors are just the pipeline config being invalid (probably missing required fields or bad YAML indentation). No damage done to your actual codebase. Pipelines don't modify your source code; they only run CI/CD steps on it.

Here's how to remove it:

Go to your repository in Bitbucket Cloud.
Find the bitbucket-pipelines.yml file in the root of your repo (it'll be in the source view).
Delete that file and commit the change. That alone stops any pipeline from running.
Then head to Repository settings > Pipelines > Settings and toggle the "Enable Pipelines" switch off.
That's it — you're back to square one

All comments

Ajay _view26_

Hi @Alan Holden

Here's how to remove it:

Go to your repository in Bitbucket Cloud.
Find the bitbucket-pipelines.yml file in the root of your repo (it'll be in the source view).
Delete that file and commit the change. That alone stops any pipeline from running.
Then head to Repository settings > Pipelines > Settings and toggle the "Enable Pipelines" switch off.
That's it — you're back to square one

Alan Holden

Thanks @Ajay _view26_ for the response!
There was no bitbucket-pipelines.yml file in any branch, so I created one and placed this minimal config inside.

<span>image: atlassian/default-image:3</span>
<span>pipelines:</span><span>  <br>default:</span><span>    <br>  - step:<br></span><span>      name: Build<br></span><span>        script:<br></span><span>          - echo "Pipeline configured"</span>

I'm not sure if I'm technically back to square one, because the items listed in the "Pipelines" page are still there... and pipelines was enabled back then.

Before I "Got Started", there was nothing here... or there.

But at least the red complaints have stopped... and I'll always have this lifelong reminder of something I probably should've paid someone else to do - rather than believing it was easy - and that a little "tinkering" would be easy to undo ;-]

Does anyone know why BitBucket would assume I wanted to kick off my first newbie attempt under our master production branch, rather than asking me first? Are all Pipelines supposed to go there alone?

Ajay _view26_

Hi @Alan Holden

You’re right to pause here, and I should clarify one important point: creating a `bitbucket-pipelines.yml` file is not the way to get back to square one.

If you want Pipelines fully “off” again, remove that file from the branch where it was added and disable Pipelines under **Repository settings > Pipelines > Settings**.

Screenshot 2026-07-15 at 9.44.13 AM.png

The entries already shown on the **Pipelines** page are pipeline history/status records. They can remain visible even after you remove the YAML file or turn Pipelines off, but they don’t mean a pipeline is still configured or actively doing anything.

On the branch question: Bitbucket isn’t treating `master` as special for Pipelines because it is “production”; it is most likely using it because it is your repository’s default branch, or because that is the branch where the setup flow/config file was created. Pipelines can run on any branch that contains `bitbucket-pipelines.yml`.

Also, this part is important:

  yaml
pipelines:
default:

default here does not mean “the master/default branch.” It means “run this pipeline for pushes to branches that do not have a more specific branch rule.”

Alan Holden

When a user is following a link that says "Getting Started..." it's easy to assume that that user doesn't know a lot about the process.

Is it unreasonable to simply confirm which branch the user wanted to "Get Started" with?

(a hypothetical question to nobody in particular)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

pipelines