Expose last mirror sync timestamp through the API #8352

New Issue

GiteaMirror · 2025-11-02T08:03:25-06:00

GiteaMirror commented

2025-11-02 08:03:25 -06:00

Originally created by @petergardfjall on GitHub (Jan 14, 2022).

Feature Description

One can queue up a sync operation for a mirror repo via POST /api/v1/{owner}/{repo}/mirror-sync.
However, there is no way for an API client of learning of completion (the UI does expose this information in the Last update mirror setting field, but not the REST API).

This issue proposes to add a mirror_updated field to the repository type (as returned by GET /api/v1/{owner}/{repo}).
For example, this allows API clients to determine if an initiated sync has completed, or take decisions on if a mirror repo should be synced (given some client-side policy on freshness).

Originally created by @petergardfjall on GitHub (Jan 14, 2022). ### Feature Description One can queue up a sync operation for a mirror repo via `POST /api/v1/{owner}/{repo}/mirror-sync`. However, there is no way for an API client of learning of completion (the _UI_ does expose this information in the `Last update` mirror setting field, but not the REST API). This issue proposes to add a `mirror_updated` field to the repository type (as returned by `GET /api/v1/{owner}/{repo}`). For example, this allows API clients to determine if an initiated sync has completed, or take decisions on if a mirror repo should be synced (given some client-side policy on freshness).

GiteaMirror added the type/feature modifies/api labels 2025-11-02 08:03:25 -06:00

GiteaMirror closed this issue

2025-11-02 08:03:25 -06:00

GiteaMirror commented

2025-11-02 08:03:26 -06:00

@petergardfjall commented on GitHub (Jan 14, 2022):

PR in https://github.com/go-gitea/gitea/pull/18267

@petergardfjall commented on GitHub (Jan 14, 2022): PR in https://github.com/go-gitea/gitea/pull/18267

Sign in to join this conversation.