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

Optimize Dependency Cloning by Reusing Clones #2

Open
euforic opened this issue Sep 14, 2023 · 0 comments
Open

Optimize Dependency Cloning by Reusing Clones #2

euforic opened this issue Sep 14, 2023 · 0 comments

Comments

@euforic
Copy link
Owner

euforic commented Sep 14, 2023

Problem

At present, our workflow clones dependencies every single time they're needed and subsequently deletes them after use. This process can be inefficient, especially if the dependencies don't change frequently.

Proposed Solution

To improve efficiency and reduce the operational overhead, we should consider modifying our approach:

  1. Clone Once: If a dependency doesn't already exist locally, clone it.
  2. Reuse: If a dependency has already been cloned previously, reuse the existing clone rather than fetching it again. This will save on network and processing overhead.
  3. Update: Periodically check for updates to dependencies and pull changes if needed.

By adopting this approach, we can reduce unnecessary network traffic, speed up operations, and make our process more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant