Skip to content

Expose last mirror sync timestamp through the API #18266

Closed
@petergardfjall

Description

@petergardfjall
Contributor

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).

Activity

petergardfjall

petergardfjall commented on Jan 14, 2022

@petergardfjall
ContributorAuthor

PR in #18267

added
type/featureCompletely new functionality. Can only be merged if feature freeze is not active.
modifies/apiThis PR adds API routes or modifies them
on Jan 15, 2022
added a commit that references this issue on Jan 18, 2022
89a3214
added a commit that references this issue on Mar 28, 2022
388fbb1
locked and limited conversation to collaborators on Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    modifies/apiThis PR adds API routes or modifies themtype/featureCompletely new functionality. Can only be merged if feature freeze is not active.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @petergardfjall@zeripath

      Issue actions

        Expose last mirror sync timestamp through the API · Issue #18266 · go-gitea/gitea