[GH-ISSUE #225] [feat. request] sorting repository table #471

New Issue

GiteaMirror · 2026-04-13T14:12:04-05:00

GiteaMirror commented

2026-04-13 14:12:04 -05:00

Originally created by @kapdon on GitHub (Mar 14, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/225

Originally assigned to: @arunavo4 on GitHub.

I want to add sorting feature to the repository table, mainly so I can show recently imported repository on top.

my first pass on this has a few gaps that need to be addressed from a architecture perspective.

created_at stores the GitHub creation date, not the import date

When repositories are imported from GitHub, the createdAt field is populated from GitHub's repo.created_at timestamp (src/lib/github.ts:290,351,495). This means sorting by "date added" isn't possible with the current schema.
we'd be sorting by when the repo was created on GitHub, which isn't useful for understanding when a user added it to the mirror system.

Deriving import date from the activities/jobs table is expensive

The mirrorJobs table tracks import events (jobType: "import"), so technically we could look up when a repo was first imported by querying the earliest job record. However, this would require a join or subquery per repository at render time, which is expensive — especially for users with hundreds of repos. This approach also breaks down if job history is cleaned up by the cleanup service.

Mobile table is a separate implementation on the frontend it seems, I didn't look at this too much.

Proposal:

Add a dedicated importedAt timestamp column to the repositories table in src/lib/db/schema.ts

Backfill strategy for existing data:

we can use current unixepoch() for those that don't have an exiting record.
or the migration can default to the current createdAt value.

It won't be perfectly accurate (it'll reflect the GitHub creation date), but it's a reasonable approximation for existing data.

let me know your thoughts

Originally created by @kapdon on GitHub (Mar 14, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/225 Originally assigned to: @arunavo4 on GitHub. I want to add sorting feature to the repository table, mainly so I can show recently imported repository on top. my first pass on this has a few gaps that need to be addressed from a architecture perspective. 1. created_at stores the GitHub creation date, not the import date When repositories are imported from GitHub, the createdAt field is populated from GitHub's repo.created_at timestamp (src/lib/github.ts:290,351,495). This means sorting by "date added" isn't possible with the current schema. we'd be sorting by when the repo was created on GitHub, which isn't useful for understanding when a user added it to the mirror system. 2. Deriving import date from the activities/jobs table is expensive The mirrorJobs table tracks import events (jobType: "import"), so technically we could look up when a repo was first imported by querying the earliest job record. However, this would require a join or subquery per repository at render time, which is expensive — especially for users with hundreds of repos. This approach also breaks down if job history is cleaned up by the cleanup service. 3. Mobile table is a separate implementation on the frontend it seems, I didn't look at this too much. ## Proposal: Add a dedicated importedAt timestamp column to the repositories table in src/lib/db/schema.ts ### Backfill strategy for existing data: - we can use current unixepoch() for those that don't have an exiting record. - or the migration can default to the current createdAt value. It won't be perfectly accurate (it'll reflect the GitHub creation date), but it's a reasonable approximation for existing data. let me know your thoughts

GiteaMirror closed this issue

2026-04-13 14:12:05 -05:00

GiteaMirror commented

2026-04-13 14:12:07 -05:00

@arunavo4 commented on GitHub (Mar 15, 2026):

Implemented in #226.

What we changed

Added repositories.imported_at (NOT NULL, default unixepoch()).
Added index: (user_id, imported_at) for fast user-scoped sorting.
Updated /api/github/repositories default ordering to importedAt DESC, then name.
Included importedAt in repository response typing.

How imported time is determined

New imports: set importedAt = now in GitHub import/sync flows.
Existing rows (migration backfill): use earliest matching mirror_jobs.timestamp where status='imported'.
- Match by repository_id when present.
- Fallback match by normalized repository name/full-name when repository_id is missing.
Final fallback: if no job match exists, use repositories.created_at.

Sorting outcome

Repository list now has a stable "recently imported first" default based on real import time.
This avoids drift from mutable fields and gives predictable sorting for users.

@arunavo4 commented on GitHub (Mar 15, 2026): Implemented in #226. ### What we changed - Added `repositories.imported_at` (`NOT NULL`, default `unixepoch()`). - Added index: `(user_id, imported_at)` for fast user-scoped sorting. - Updated `/api/github/repositories` default ordering to `importedAt DESC`, then name. - Included `importedAt` in repository response typing. ### How imported time is determined - **New imports:** set `importedAt = now` in GitHub import/sync flows. - **Existing rows (migration backfill):** use earliest matching `mirror_jobs.timestamp` where `status='imported'`. - Match by `repository_id` when present. - Fallback match by normalized repository name/full-name when `repository_id` is missing. - **Final fallback:** if no job match exists, use `repositories.created_at`. ### Sorting outcome - Repository list now has a stable "recently imported first" default based on real import time. - This avoids drift from mutable fields and gives predictable sorting for users.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#471