Collection structure not maintained when cloning a Github Repo

[rreyn-bruno]

I have checked the following:

• [x] I have searched existing issues and found nothing related to my issue.

This bug is:

• [ ] making Bruno unusable for me
• [x] slowing me down but I'm able to continue working
• [x] annoying
• [ ] this feature was working in a previous version but is broken in the current release.

Bruno version

2.3.0

Operating System

Sequoia 15.1

Describe the bug

When importing this Bruno collection https://github.com/bruno-collections/bruno-starter-guide, the structure of the collection is not maintained.

Also, should this 'assets' folder be imported?

.bru file to reproduce the bug

No response

Screenshots/Live demo link

https://github.com/bruno-collections/bruno-starter-guide

[fantpmas]

Same issue here.

[helloanoop]

@lohit-bruno I think the recent updates we made for folder sequencing could have caused this. Can you take a look.

Also @rreyn-bruno the assets folder would be visible since it's inside the collection. You should be able to ignore this by adding to the ignores config in bruno.json

{
  "version": "1",
  "name": "collection_name",
  "type": "collection",
  "ignore": ["assets"]
}

[fantpmas]

Any idea when this will be taken up? This is preventing us from updating.

[rreyn-bruno]

Adding context that this issue doesn't just occur when cloning/importing a collection, but also purely by upgrading Bruno past V2.2.0.

We've spent a lot of time during the migration to Bruno reordering collections/folders. We've build scripts using sub-folder names to indicate their desired order. For example:

On upgrade from Bruno v2.2.0 to v2.4.0 it was noticed that the order of the sub-folders had become “randomized”. The order could be corrected by dragging them into the desired order, which creates corresponding folder.bru files. However, we don’t want to have to do this for all of our test scripts.

We have reverted to v2.2.0.