Skip to content

Debounce dab repo fetch #377

@Nekroze

Description

@Nekroze

Change Request

Please describe the current behaviour

At present dab repo fetch always fetches from git remotes.

What is suboptimal about the current behaviour

The current behaviour is insufficient because it may be run many times in quick succession.

Describe the way you think it should behave

Using a similar time based mechanism as the auto update debouncing record when each repo was last fetched.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions