[Feature] sort repository #11131

Originally created by @TimerWolf on GitHub (Jun 29, 2023).

Feature Description

Why is it not possible to sort the order of the information inside a repository, after all it is a list ?

It would be nice if "files / folders" could be sorted after "files / folders" maybe after "name" or the commits could be sorted after "name" or why not the "commits dates" be sorted after "first / last" commit ?

I do not see why this not possible, and not implanted as it should be in my eyes very neat and obvious function.

And know i am not sure how it is sorted by default, but as well maybe have a setting under the user account that lets you set the "default" order it should be sorted in, if it are after ("file/folder name" / commit / date) as an example

Screenshots

No response

Originally created by @TimerWolf on GitHub (Jun 29, 2023). ### Feature Description Why is it not possible to sort the order of the information inside a repository, after all it is a list ? It would be nice if "files / folders" could be sorted after "files / folders" maybe after "name" or the commits could be sorted after "name" or why not the "commits dates" be sorted after "first / last" commit ? I do not see why this not possible, and not implanted as it should be in my eyes very neat and obvious function. And know i am not sure how it is sorted by default, but as well maybe have a setting under the user account that lets you set the "default" order it should be sorted in, if it are after ("file/folder name" / commit / date) as an example ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 09:28:30 -06:00

GiteaMirror commented

@silverwind commented on GitHub (Jun 29, 2023):

I don't see much use of sorting the files table and to make it sortable, some headers would likely needed to be added which imho bloats the UI. Sort by commit name is almost always useless. Sort by commit date is semi-useful, but I think more often than not people are looking for a file than for commit dates.

@silverwind commented on GitHub (Jun 29, 2023): I don't see much use of sorting the files table and to make it sortable, some headers would likely needed to be added which imho bloats the UI. Sort by commit name is almost always useless. Sort by commit date is semi-useful, but I think more often than not people are looking for a file than for commit dates.

GiteaMirror commented

@TimerWolf commented on GitHub (Jun 29, 2023):

It was just an example, what i was after was to sort after name but while you add the "sorting function" if it would be added it never bad to have some extra features if anyone would like them.....

@TimerWolf commented on GitHub (Jun 29, 2023): It was just an example, what i was after was to sort after name but while you add the "sorting function" if it would be added it never bad to have some extra features if anyone would like them.....

GiteaMirror commented

@mpeter50 commented on GitHub (Jul 1, 2023):

You mean sorting the files of a repository, right? Isn't it already sorted by name?

@mpeter50 commented on GitHub (Jul 1, 2023): You mean sorting the files of a repository, right? Isn't it already sorted by name?

GiteaMirror commented

@TimerWolf commented on GitHub (Jul 2, 2023):

Not if you look at my repo on this image, maybe it is a bug?

@TimerWolf commented on GitHub (Jul 2, 2023): Not if you look at my repo on this image, maybe it is a bug? ![alt text](https://i.imgur.com/aK7iOvI.png)

GiteaMirror commented

@mpeter50 commented on GitHub (Jul 2, 2023):

That is interesting. Maybe the devs can shed some light on it.

What I do know is that in most cases, it looks to be sorted by filename, whether it is a directory, and wthether it is hidden (starts with a dot):

Also, I just noticed that names starting with uppercase letters are sorted earlier, too.
From you Ctrl+F-ing it looks they all start with the same characters until the number. Maybe there are inivisble characters before or after some of the names highlighted part, or some of the numbers are weird alternatives of the actual numbers?

Maybe you could look in the browser developer tools to see if theres an invisible difference thats shown here.

@mpeter50 commented on GitHub (Jul 2, 2023): That is interesting. Maybe the devs can shed some light on it. What I do know is that in most cases, it looks to be sorted by filename, whether it is a directory, and wthether it is hidden (starts with a dot): - https://gitea.com/gitea/gitea_mirror - https://gitea.com/gitea/tea - https://codeberg.org/jannis/FitoTrack/ - https://codeberg.org/Freeyourgadget/Gadgetbridge Also, I just noticed that names starting with uppercase letters are sorted earlier, too. From you Ctrl+F-ing it looks they all start with the same characters until the number. Maybe there are inivisble characters before or after some of the names highlighted part, or some of the numbers are weird alternatives of the actual numbers? Maybe you could look in the browser developer tools to see if theres an invisible difference thats shown here.

GiteaMirror commented

@delvh commented on GitHub (Jul 2, 2023):

If I'm not mistaken, the sort order is the one Git returns.
And Git should return the files in alphabetic order by default.
The fact that this is not the case for you indicates one of two things for me:

Your v8 filename contains an invisible space for some reason (i.e. a zero-width-space)
Git has a bug…

I don't see many other options right now.

@delvh commented on GitHub (Jul 2, 2023): If I'm not mistaken, the sort order is the one Git returns. And Git should return the files in alphabetic order by default. The fact that this is not the case for you indicates one of two things for me: 1. Your `v8` filename contains an invisible space for some reason (i.e. a zero-width-space) 2. Git has a bug… I don't see many other options right now.

GiteaMirror commented

@silverwind commented on GitHub (Jul 7, 2023):

Try git ls-files to see the order git returns.

@silverwind commented on GitHub (Jul 7, 2023): Try `git ls-files` to see the order git returns.

GiteaMirror commented

@TimerWolf commented on GitHub (Jul 10, 2023):

Maybe that´s the problem, this "git directory" is created in "gitea" and do not have any "offline" repository.

@TimerWolf commented on GitHub (Jul 10, 2023): Maybe that´s the problem, this "git directory" is created in "gitea" and do not have any "offline" repository.

GiteaMirror commented

@delvh commented on GitHub (Jul 10, 2023):

I am quite confused by what you mean.
Gitea is in this regard simply a proxy for Git:
We simply query all file and commit-related information from Git.
If it it doesn't exist for Git, it doesn't exist for Gitea.

@delvh commented on GitHub (Jul 10, 2023): I am quite confused by what you mean. Gitea is in this regard simply a proxy for Git: We simply query all file and commit-related information from Git. If it it doesn't exist for Git, it doesn't exist for Gitea.

GiteaMirror commented

@mpeter50 commented on GitHub (Jul 10, 2023):

Do you mean that the repository was created in Gitea, and you don't have access to its files on your PC?
If so, this shouldn't cause what you experience.

Try cloning the repo and running the mentioned command that way.

@mpeter50 commented on GitHub (Jul 10, 2023): Do you mean that the repository was created in Gitea, and you don't have access to its files on your PC? If so, this shouldn't cause what you experience. Try cloning the repo and running the mentioned command that way.

GiteaMirror commented

@TimerWolf commented on GitHub (Jul 11, 2023):

Exactly like that but i did try to rename it and it did work....

I will keep my eyes open as i do not think it was any "hidden/wrong" char in it before but you should never say never...

@TimerWolf commented on GitHub (Jul 11, 2023): Exactly like that but i did try to rename it and it did work.... I will keep my eyes open as i do not think it was any "hidden/wrong" char in it before but you should never say never...

GiteaMirror commented