Update RepositoryBranchNamesResolver to sort branch names
From this comment:
Also as a side note, I noticed a bit of annoying behavior that the branches returned are not sorted alphabetically (or any order for that matter, not even by created at or similar). I checked and this is likely something we have to update on the backend here. Just a small improvement IMO, not something we have to do urgently.
We should update the backend code to have some sort of sorting that makes sense (alphabetical, by created at, by updated at...). Maybe we can always put the default / protected branches (master
, main
, dev
...) on top, then include the others.
Existing behaviour
Branches returned do not have any default or configurable sort order.
Expected behaviour
The query should provide some default sort order (maybe similar to the branch listing under project repository) or allow it to be configured.
This would provide better UX for users, especially when there are branches with similar names.