Skip to content

Allow sorting patches by committer - #123

Merged
JelteF merged 3 commits into
postgres:mainfrom
jonasrochasilva-prog:feat/sort-by-committer
Oct 18, 2026
Merged

JelteF merged 3 commits into
postgres:mainfrom
jonasrochasilva-prog:feat/sort-by-committer

Conversation

@jonasrochasilva-prog

@jonasrochasilva-prog jonasrochasilva-prog commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Fixes #112

The Committer column on the commitfest page can now be clicked to sort by committer, like the other columns. Combined with the Committed status filter this makes it easy to see who committed what in a commitfest.

On the page of a commitfest, the Committer column header can now be
clicked to sort the patch list by committer, just like the other
sortable columns. Combined with the Committed status filter, this makes
it easy to see who committed what in a commitfest.

Committers are sorted by last name, then first name and username, which
is the same order that the Committer model uses. Patches without a
committer are always shown last, and the patch ID is used as a
tiebreaker. Like with the other sort orders, open patches are still
shown before closed ones.

The dashboard is left unchanged, since this was only requested for the
commitfest page.

Fixes postgres#112
@@ -0,0 +1,189 @@
from django.contrib.auth.models import User

@JelteF JelteF Oct 18, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove this test. I think a generic sorting test could be useful for coverage. But this is way to specialised on this specific sorting method. Generic sorting test should be a separate PR.

FennemAI and others added 2 commits October 18, 2026 09:58
The tests were very specialised to this one sort method. A generic test covering all sort keys would be more useful and belongs in a separate PR.
Descending kept patches without a committer at the bottom and kept the
`p.id` tiebreaker ascending, so clicking the header again didn't reverse
the list. Now it does. Since PostgreSQL already sorts NULLs last when
ascending and first when descending, the explicit `NULLS LAST` clauses
are no longer needed.
@JelteF
JelteF merged commit 60d5a29 into postgres:main Oct 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow sorting by committer

3 participants