Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Disable pipelines read access rights for public repositories

Is it possible to disable access to the `Pipelines` menu for public repositories?


In other words, for any user, the `Pipelines` menu would not appear and would not be accessible.

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 18, 2023

Hi @zoltan_zvara,

I'm afraid that this is not possible. When a repository is public, all of its pages are publicly available (except the Repository settings page, which is only available to admins).

If you have a public repo (which means that the bitbucket-pipelines.yml file is also public), could you please explain why you are looking to make the Pipelines page private?

Kind regards,

I'm worried the pipeline would log a credential, like a password or PAT, into the build logs by mistake. On the other hand, the consumer of the said repository is not interested in the pipeline itself, therefore, disabling that menu item would simplify a lot of stuff an increase security.

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 19, 2023

Hi @zoltan_zvara,

Thank you for the details. Would it work for you if you kept this repo private and created a public fork of the repo to share?

When you create a fork of a repo, the Pipelines builds and the repository variables do not get transferred to the fork. Pipelines is by default disabled in the fork (unless you manually enable it from Repository settings > Settings (under the section PIPELINES), so a build will not run when you sync/update the fork.

Please keep in mind that a fork is not synced automatically, it can only be synced manually:

Additionally, the sync operation syncs the main branch of the repo only. You could write a script though that syncs all branches (if that is a requirement) and run it on set intervals to update the fork.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events