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

Use actual diff information instead of re-scanning the whole tree #4

Open
jamwt opened this issue Sep 9, 2023 · 0 comments
Open

Use actual diff information instead of re-scanning the whole tree #4

jamwt opened this issue Sep 9, 2023 · 0 comments
Labels
difficult Larger or more exploratory tasks/refactorings enhancement New feature or request good first issue Good for newcomers

Comments

@jamwt
Copy link
Contributor

jamwt commented Sep 9, 2023

Right now, to keep things simple, dryad uses the GitHub API to grab the entire file tree for whatever commit is at HEAD. It then checks every single file against the database to see if anything has changed.

A more optimal approach (especially for big repositories) would be to consume each commit on the target branch and actually use the commit's information about what file(s) changed. Then only reindex (or delete) those.

@jamwt jamwt added enhancement New feature or request good first issue Good for newcomers difficult Larger or more exploratory tasks/refactorings labels Sep 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficult Larger or more exploratory tasks/refactorings enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant