Skip to content

Change default sorting of user/org search to alphabetical #2656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 7 tasks
daviian opened this issue Oct 4, 2017 · 3 comments
Closed
1 of 7 tasks

Change default sorting of user/org search to alphabetical #2656

daviian opened this issue Oct 4, 2017 · 3 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone
1.3.0

Comments

@daviian
Copy link
Member

daviian commented Oct 4, 2017

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL) search on explore page for user/org
    • No
    • Not relevant
  • Log gist:

Description

At the moment every page including a searchbox use the same searchbox template, thus every search uses the same default ordering.
IMO sorting users and organizations by newest doesn't make much sense.
It would be more natural to have it sorted alphabetically by default.

I think in order to achieve that, we have to change the searchbox template to allow a dynamic assignment of default ordering per page.
@lafriks lafriks added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Oct 4, 2017
@lafriks lafriks added this to the 1.x.x milestone Oct 4, 2017
@kaz kaz mentioned this issue Oct 4, 2017
Merged
@sapk
Copy link
Member

sapk commented Oct 5, 2017

Order by last activity could be best.

@daviian
Copy link
Member Author

daviian commented Oct 5, 2017

@sapk Since #2647 has already been merged ticket should be closed by now. ;-)

@daviian daviian closed this as completed Oct 5, 2017
@lafriks
Copy link
Member

lafriks commented Oct 5, 2017

@sapk it is very hard to orientate in searchbox if users are not alphabetically

@lunny lunny modified the milestones: 1.x.x, 1.3.0 Oct 7, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
@Gusted
[BUG] Use correct head commit for CODEOWNER
d1cebb0 
Backport of go-gitea#2658

Regression of go-gitea#2507, which switched the HEAD from `pr.GetGitRefName()`
to `pr.HeadCommitID` but it had to be `prInfo.HeadCommitID`. Resolves go-gitea#2656
I was able to reproduce this locally with _some_ pull requests, haven't
been able to get a reproducer trough integration testing.

(cherry picked from commit a4cc37b)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
1.3.0
Development

No branches or pull requests
4 participants
@lunny @lafriks @sapk @daviian