Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Project structure issue (inside a repo) Edited

Wanted to see, in my branch, the top level folders only (project structure) but because I have only 1 sub-folder in some of them (see example below), I see that "glue" effect :-( - how to fix that?
If there are more than one sub-folder in a folder then it looks Ok (as Top1 and Top3 below)

Top2/<single sub-folder name>
Top4/<single sub-folder name>



Note. There is a solution for similar issue in IntelliJ - may be it will be helpful?
When I open same project in IntelliJ (where folders and sub-folders are "packages") I initially saw the same "bad looking" project structure, but then found the solution and now I have clean/normal project structure in IntelliJ:

"Create non-flat packages":
'In the project pane, click the gear in the top right corner, and un-select "compact empty middle packages".'

1 answer

1 accepted

0 votes
Answer accepted

Hi @pgorodyansky,

This behavior is by design, as it is a feature of Bitbucket to 'collapse' directories which contain only a single subdirectory into a single composite directory.

For example, consider the following repository layout (which is very common for Java projects using Maven):



When listing src, both main and test each contain only a single subdirectory, which itself contains only a single subdirectory. That repeats for several layers of nesting. Without collapsing, navigating the directory structure would require clicking through several layers, with each layer requiring a server roundtrip to load the next. Both of these, combined, would lead to a great deal of annoyance for the user as well as increased load on the server as it handles each individual call.

While there's no form of configuration value or toggle to prevent this functionality, it's unlikely that this would be implemented - as any use case for not completing this directory collapse is usually something better handled by alternative solutions such as using something like git submodules to split out multiple 'projects' within a currently monolithic repository.

Hope this helps!


Evan Slaughter

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

525 views 6 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you