Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debounce dab repo fetch #377

Open
Nekroze opened this issue Mar 12, 2019 · 0 comments
Open

Debounce dab repo fetch #377

Nekroze opened this issue Mar 12, 2019 · 0 comments
Labels
optimization Tuning for performance
Projects

Comments

@Nekroze
Copy link
Owner

Nekroze commented Mar 12, 2019

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.

@Nekroze Nekroze added the optimization Tuning for performance label Mar 12, 2019
@Nekroze Nekroze added this to Probably Soonish in Roadmap Mar 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimization Tuning for performance
Projects
Roadmap
Probably Soonish
Development

No branches or pull requests

1 participant