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

Prevent unnecessary clones #64

Open
jansenignacio opened this issue Aug 10, 2021 · 1 comment
Open

Prevent unnecessary clones #64

jansenignacio opened this issue Aug 10, 2021 · 1 comment
Assignees
Labels

Comments

@jansenignacio
Copy link

This feature request adds a lot of complexity to this project but here it is anyway

PROBLEM:
Suppose you have a constant list of 10 repos you want to use Turbolift for. Each and every campaign you create will result in a new clone of the repos. This takes up unnecessary space on a dev's local drive, plus it's slow to download them over and over.

FEATURE REQUEST:
Allow to define a localpath in repos.txt which indicates a local clone of a repository to be worked on. Use this clone instead of creating a new one in the work directory for every new campaign

ALTERNATIVE APPROACH:
Allow to define a repos.txt (or core_repos.txt) in the root of a turbolift directory (this also invents this concept). These core_repos are what you expect to work on most of the time, and thus shouldn't re-clone everytime. There would also be a work directory beside the core_repos.txt.

The file structure would look something like this:

/turbolift_project
--core_repos.txt
--/work
----/repo1
----/repo2
--/campaign_1
----repos.txt
----/work
------/repo3
--/capmpaign_2
----/repos.txt
----/work
------/repo4
@sledigabel
Copy link
Contributor

Thanks a lot for raising this @jansenignacio!
We had a previous internal version of the tool that worked like that based off git worktree and did exactly what you describe. I'll add some more details based on that issue a bit later.

@sledigabel sledigabel self-assigned this Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants